commit 49bb576fc03c1f5b33800db6d46aff18159c81da
Author: Simon Watson <spw01@protonmail.com>
Date: Wed Oct 27 21:13:11 2021 -0400
Finished emacs blog post
diff --git a/2021-emacs-windows.html b/2021-emacs-windows.html
new file mode 100644
index 0000000..ef704ce
--- /dev/null
+++ b/2021-emacs-windows.html
@@ -0,0 +1,404 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<!-- 2021-10-27 Wed 21:02 -->
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<title></title>
+<meta name="generator" content="Org mode" />
+<meta name="author" content="Simon Watson" />
+<style type="text/css">
+ <!--/*--><![CDATA[/*><!--*/
+ .title { text-align: center;
+ margin-bottom: .2em; }
+ .subtitle { text-align: center;
+ font-size: medium;
+ font-weight: bold;
+ margin-top:0; }
+ .todo { font-family: monospace; color: red; }
+ .done { font-family: monospace; color: green; }
+ .priority { font-family: monospace; color: orange; }
+ .tag { background-color: #eee; font-family: monospace;
+ padding: 2px; font-size: 80%; font-weight: normal; }
+ .timestamp { color: #bebebe; }
+ .timestamp-kwd { color: #5f9ea0; }
+ .org-right { margin-left: auto; margin-right: 0px; text-align: right; }
+ .org-left { margin-left: 0px; margin-right: auto; text-align: left; }
+ .org-center { margin-left: auto; margin-right: auto; text-align: center; }
+ .underline { text-decoration: underline; }
+ #postamble p, #preamble p { font-size: 90%; margin: .2em; }
+ p.verse { margin-left: 3%; }
+ pre {
+ border: 1px solid #ccc;
+ box-shadow: 3px 3px 3px #eee;
+ padding: 8pt;
+ font-family: monospace;
+ overflow: auto;
+ margin: 1.2em;
+ }
+ pre.src {
+ position: relative;
+ overflow: auto;
+ padding-top: 1.2em;
+ }
+ pre.src:before {
+ display: none;
+ position: absolute;
+ background-color: white;
+ top: -10px;
+ right: 10px;
+ padding: 3px;
+ border: 1px solid black;
+ }
+ pre.src:hover:before { display: inline; margin-top: 14px;}
+ /* Languages per Org manual */
+ pre.src-asymptote:before { content: 'Asymptote'; }
+ pre.src-awk:before { content: 'Awk'; }
+ pre.src-C:before { content: 'C'; }
+ /* pre.src-C++ doesn't work in CSS */
+ pre.src-clojure:before { content: 'Clojure'; }
+ pre.src-css:before { content: 'CSS'; }
+ pre.src-D:before { content: 'D'; }
+ pre.src-ditaa:before { content: 'ditaa'; }
+ pre.src-dot:before { content: 'Graphviz'; }
+ pre.src-calc:before { content: 'Emacs Calc'; }
+ pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
+ pre.src-fortran:before { content: 'Fortran'; }
+ pre.src-gnuplot:before { content: 'gnuplot'; }
+ pre.src-haskell:before { content: 'Haskell'; }
+ pre.src-hledger:before { content: 'hledger'; }
+ pre.src-java:before { content: 'Java'; }
+ pre.src-js:before { content: 'Javascript'; }
+ pre.src-latex:before { content: 'LaTeX'; }
+ pre.src-ledger:before { content: 'Ledger'; }
+ pre.src-lisp:before { content: 'Lisp'; }
+ pre.src-lilypond:before { content: 'Lilypond'; }
+ pre.src-lua:before { content: 'Lua'; }
+ pre.src-matlab:before { content: 'MATLAB'; }
+ pre.src-mscgen:before { content: 'Mscgen'; }
+ pre.src-ocaml:before { content: 'Objective Caml'; }
+ pre.src-octave:before { content: 'Octave'; }
+ pre.src-org:before { content: 'Org mode'; }
+ pre.src-oz:before { content: 'OZ'; }
+ pre.src-plantuml:before { content: 'Plantuml'; }
+ pre.src-processing:before { content: 'Processing.js'; }
+ pre.src-python:before { content: 'Python'; }
+ pre.src-R:before { content: 'R'; }
+ pre.src-ruby:before { content: 'Ruby'; }
+ pre.src-sass:before { content: 'Sass'; }
+ pre.src-scheme:before { content: 'Scheme'; }
+ pre.src-screen:before { content: 'Gnu Screen'; }
+ pre.src-sed:before { content: 'Sed'; }
+ pre.src-sh:before { content: 'shell'; }
+ pre.src-sql:before { content: 'SQL'; }
+ pre.src-sqlite:before { content: 'SQLite'; }
+ /* additional languages in org.el's org-babel-load-languages alist */
+ pre.src-forth:before { content: 'Forth'; }
+ pre.src-io:before { content: 'IO'; }
+ pre.src-J:before { content: 'J'; }
+ pre.src-makefile:before { content: 'Makefile'; }
+ pre.src-maxima:before { content: 'Maxima'; }
+ pre.src-perl:before { content: 'Perl'; }
+ pre.src-picolisp:before { content: 'Pico Lisp'; }
+ pre.src-scala:before { content: 'Scala'; }
+ pre.src-shell:before { content: 'Shell Script'; }
+ pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
+ /* additional language identifiers per "defun org-babel-execute"
+ in ob-*.el */
+ pre.src-cpp:before { content: 'C++'; }
+ pre.src-abc:before { content: 'ABC'; }
+ pre.src-coq:before { content: 'Coq'; }
+ pre.src-groovy:before { content: 'Groovy'; }
+ /* additional language identifiers from org-babel-shell-names in
+ ob-shell.el: ob-shell is the only babel language using a lambda to put
+ the execution function name together. */
+ pre.src-bash:before { content: 'bash'; }
+ pre.src-csh:before { content: 'csh'; }
+ pre.src-ash:before { content: 'ash'; }
+ pre.src-dash:before { content: 'dash'; }
+ pre.src-ksh:before { content: 'ksh'; }
+ pre.src-mksh:before { content: 'mksh'; }
+ pre.src-posh:before { content: 'posh'; }
+ /* Additional Emacs modes also supported by the LaTeX listings package */
+ pre.src-ada:before { content: 'Ada'; }
+ pre.src-asm:before { content: 'Assembler'; }
+ pre.src-caml:before { content: 'Caml'; }
+ pre.src-delphi:before { content: 'Delphi'; }
+ pre.src-html:before { content: 'HTML'; }
+ pre.src-idl:before { content: 'IDL'; }
+ pre.src-mercury:before { content: 'Mercury'; }
+ pre.src-metapost:before { content: 'MetaPost'; }
+ pre.src-modula-2:before { content: 'Modula-2'; }
+ pre.src-pascal:before { content: 'Pascal'; }
+ pre.src-ps:before { content: 'PostScript'; }
+ pre.src-prolog:before { content: 'Prolog'; }
+ pre.src-simula:before { content: 'Simula'; }
+ pre.src-tcl:before { content: 'tcl'; }
+ pre.src-tex:before { content: 'TeX'; }
+ pre.src-plain-tex:before { content: 'Plain TeX'; }
+ pre.src-verilog:before { content: 'Verilog'; }
+ pre.src-vhdl:before { content: 'VHDL'; }
+ pre.src-xml:before { content: 'XML'; }
+ pre.src-nxml:before { content: 'XML'; }
+ /* add a generic configuration mode; LaTeX export needs an additional
+ (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
+ pre.src-conf:before { content: 'Configuration File'; }
+
+ table { border-collapse:collapse; }
+ caption.t-above { caption-side: top; }
+ caption.t-bottom { caption-side: bottom; }
+ td, th { vertical-align:top; }
+ th.org-right { text-align: center; }
+ th.org-left { text-align: center; }
+ th.org-center { text-align: center; }
+ td.org-right { text-align: right; }
+ td.org-left { text-align: left; }
+ td.org-center { text-align: center; }
+ dt { font-weight: bold; }
+ .footpara { display: inline; }
+ .footdef { margin-bottom: 1em; }
+ .figure { padding: 1em; }
+ .figure p { text-align: center; }
+ .equation-container {
+ display: table;
+ text-align: center;
+ width: 100%;
+ }
+ .equation {
+ vertical-align: middle;
+ }
+ .equation-label {
+ display: table-cell;
+ text-align: right;
+ vertical-align: middle;
+ }
+ .inlinetask {
+ padding: 10px;
+ border: 2px solid gray;
+ margin: 10px;
+ background: #ffffcc;
+ }
+ #org-div-home-and-up
+ { text-align: right; font-size: 70%; white-space: nowrap; }
+ textarea { overflow-x: auto; }
+ .linenr { font-size: smaller }
+ .code-highlighted { background-color: #ffff00; }
+ .org-info-js_info-navigation { border-style: none; }
+ #org-info-js_console-label
+ { font-size: 10px; font-weight: bold; white-space: nowrap; }
+ .org-info-js_search-highlight
+ { background-color: #ffff00; color: #000000; font-weight: bold; }
+ .org-svg { width: 90%; }
+ /*]]>*/-->
+</style>
+<script type="text/javascript">
+// @license magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=public-domain.txt Public Domain
+<!--/*--><![CDATA[/*><!--*/
+ function CodeHighlightOn(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.add("code-highlighted");
+ target.classList.add("code-highlighted");
+ }
+ }
+ function CodeHighlightOff(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.remove("code-highlighted");
+ target.classList.remove("code-highlighted");
+ }
+ }
+ /*]]>*///-->
+// @license-end
+</script>
+</head>
+<body>
+<div id="content">
+<div id="table-of-contents">
+<h2>Table of Contents</h2>
+<div id="text-table-of-contents">
+<ul>
+<li><a href="#orgd4831a0">1. Emacs and Learning to Live with Windows</a>
+<ul>
+<li><a href="#orgb4039ce">1.1. Background/Preamble</a></li>
+<li><a href="#orge44de3f">1.2. Enter Emacs</a></li>
+<li><a href="#org1ec967f">1.3. The Beginning</a></li>
+<li><a href="#org2f6f828">1.4. Emacs Server Mode</a></li>
+<li><a href="#orgf45ed4d">1.5. Compromises and Other Thoughts</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+<p>
+</p>
+
+<div id="outline-container-orgd4831a0" class="outline-2">
+<h2 id="orgd4831a0"><span class="section-number-2">1</span> Emacs and Learning to Live with Windows</h2>
+<div class="outline-text-2" id="text-1">
+</div>
+<div id="outline-container-orgb4039ce" class="outline-3">
+<h3 id="orgb4039ce"><span class="section-number-3">1.1</span> Background/Preamble</h3>
+<div class="outline-text-3" id="text-1-1">
+<p>
+In May of 2021 I started a new job. On my first day of work I imaged my workstation with Fedora; I was coming into a
+sysadmin job in a primarily RHEL shop so this seemed appropriate. Upon getting my laptop I was informed that I could
+not install Linux on it – VPN access was Windows only.
+</p>
+
+<p>
+ "OK, no problem", I thought to myself. I'm not a huge Windows fan, and I hadn't interacted with it meaningfully since
+probably the early 00's, but I figured how bad could it be?
+</p>
+
+<p>
+As it turns out – not too bad. I was surprised to find there was some basic native window tiling behavior in the
+window manager, and with the release of the WSL and some flashy new windows terminal apps, I was pretty excited
+about how familiar it would feel.
+</p>
+
+<p>
+Unfortunately, I ran into a number of issues as I was exploring trying to get Windows to feel more Unix-y. I won't go into
+detail in this post (maybe another time), but I quickly discovered that there was a lot of muscle memory and UI workflows
+that just seemed unavailable to me in Windows (despite heroic community efforts to improve a lot of the Windows experience).
+</p>
+</div>
+</div>
+
+<div id="outline-container-orge44de3f" class="outline-3">
+<h3 id="orge44de3f"><span class="section-number-3">1.2</span> Enter Emacs</h3>
+<div class="outline-text-3" id="text-1-2">
+<p>
+Before starting this new job, I'd been a long time Vim user, but unrelated to this new job I'd started exploring Common Lisp
+programming, and as such had setup Emacs/SLIME. As part of that foray into Emacs/SLIME I'd discovered <code>eshell</code>, and as I was
+struggling to get Windows to conform to my preferred workflows I started to explore how I could use Emacs, elisp, and it's
+packages ecosystem to make my Windows experience more Unix-y.
+</p>
+</div>
+</div>
+
+<div id="outline-container-org1ec967f" class="outline-3">
+<h3 id="org1ec967f"><span class="section-number-3">1.3</span> The Beginning</h3>
+<div class="outline-text-3" id="text-1-3">
+<p>
+Initially I downloaded the Windows Emacs build and was pretty happy with the experience. I could use <code>eshell</code> to navigate
+the Windows file system in a familiar way, and had set up an <a href="https://orgmode.org/">Emacs Org mode file</a> in my company OneDrive
+that I could easily update and track my work/notes in. When I was in the office on my Fedora workstation, I could easily update
+and keep notes in my Org file and then seamlessly access them on my laptop from home.
+</p>
+
+<p>
+The problems started arising when I wanted to do development for Linux systems on my Windows laptop, and easily be able
+to edit and quickly iterate.
+</p>
+
+<p>
+First, I tried setting up the WSL so that I could have a local Linux environment to do low stakes logic tests in. Unfortunately,
+the presence of a VPN tunnel seemed to cause a lot of problems for WSL and I couldn't get networking to work correctly
+in the WSL environment. This was kind of a non starter. I spent a decent amount of time trying to unravel it, but it quickly
+became a time sink that wasn't producing anything so I gave up.
+</p>
+
+<p>
+See here for more details on this problem: <a href="https://github.com/microsoft/WSL/issues/5068">https://github.com/microsoft/WSL/issues/5068</a>
+</p>
+
+<p>
+WSL not working, I tried using <a href="https://www.emacswiki.org/emacs/TrampMode">TRAMP</a>. The idea was to just open files on my Linux workstation over
+SSH and then manage everything natively there using an SSH session. I had a number of issues that I couldn't trace down,
+but the biggest was that using the <code>plink</code> TRAMP method would indefinitely hang emacs on windows, forcing me to close it with the
+Windows task manager. As with above, had I spent a reasonable amount of time trying to debug this, I probably would've
+been able to figure out the error (which was probably a misconfiguration on my part), but as with above, it started to
+become a real time sink and I just wanted to get to work.
+</p>
+
+<p>
+Eventually, I seemed to figure out something that worked <i>beautifully</i> for all of my expected cases.
+</p>
+</div>
+</div>
+
+<div id="outline-container-org2f6f828" class="outline-3">
+<h3 id="org2f6f828"><span class="section-number-3">1.4</span> Emacs Server Mode</h3>
+<div class="outline-text-3" id="text-1-4">
+<p>
+Emacs has a <a href="https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html">server mode</a> that covered all my bases and allowed for all the flexibility I ended up needing.
+</p>
+
+<p>
+What I do is start a terminal emacs session in tmux with <code>emacs -nw</code> on my Linux workstation at the office.
+I can then do <code>M-x server-start</code> which will start the Emacs server. When I'm at home and working from my windows laptop,
+I have to use Emacs exclusively in terminal mode. This of course has some tradeoffs, but it surprisingly works very well,
+and even has great terminal mouse support (<code>M-x xterm-mouse-mode</code>). I can run any number of <code>emacsclient</code>'s in tmux windows to easily manage and organize
+all my different development projects <i>AND</i> I can access the state of any of the other sessions from whatever session I'm in, just
+using the native Emacs buffer functionality.
+</p>
+
+<p>
+Additionally, when I head into the office, I can seamlessly attach to the running Emacs server from GUI Emacs and pick up
+right where I left off.
+</p>
+</div>
+</div>
+
+<div id="outline-container-orgf45ed4d" class="outline-3">
+<h3 id="orgf45ed4d"><span class="section-number-3">1.5</span> Compromises and Other Thoughts</h3>
+<div class="outline-text-3" id="text-1-5">
+<p>
+There are a few obvious compromises with this setup.
+</p>
+
+<p>
+Firstly, I can't natively address the windows environment from my terminal, as Emacs is actually running on my Linux server. This however kind of
+turned out to be a non issue, because I'm never actually writing any software for Windows, or doing any work with it. I'm just forced to have it
+installed on my laptop.
+</p>
+
+<p>
+My sysadmin environment, for lack of a better term, has always been a large number of tmux sessions managing different
+aspects of the job. For example a tmux session for "$web Team Systems", a tmux session for "$app Team Systems", etc etc. By integrating my development environment
+into a similar tmux session, it allowed me easily hop in and out of different development contexts, regardless of which system I was using; just like
+with my "sysadmin environment".
+</p>
+
+<p>
+The immediate question that arises from this conclusion is: "Well, if you're just doing all your development in the terminal, why not just use Vim?"
+</p>
+
+<p>
+This question is not posed to restart the age old flame war, but considering that is exactly what I used to use, I should address it. The main reason is that,
+to my knowledge, I cannot run a Vim session in the terminal, and then "attach" to it with gvim (having all my tabs/files/etc open and available)
+when I come into the office and use the workstation locally.
+</p>
+
+<p>
+There are many Emacs features I've come to love, which I might cover another time, but this one feature has really got me stuck in Emacs (plus there is the
+famous <a href="https://github.com/emacs-evil/evil">EVIL mode</a>, which smooths over that transition quite a bit).
+</p>
+
+<p>
+To come back to the original point, the reason I no longer worry too much about the Windows experience is that through emacs+tmux+ssh, I don't really
+ever have to interact with Windows. It provides a basic interface to the web browser and to team communication, and virtually every other part of my
+job can be done over SSH in cygwin. In this way, I've kind of side stepped the purpose of this blog post – I've just described how to use skirt
+actually using Windows as much as possible, as opposed to addressing solving these problems in a more Windows-centric way.
+</p>
+
+<p>
+The second major compromise here (I touched on it above) is that I end up using emacs as a terminal IDE far more often than I'd like. But given the choice between
+a very robust and functional development environment available over SSH and having to go into the office every day, it's a pretty easy trade for me.
+</p>
+</div>
+</div>
+</div>
+</div>
+<div id="postamble" class="status">
+<p class="author">Author: Simon Watson</p>
+<p class="date">Created: 2021-10-27 Wed 21:02</p>
+<p class="validation"><a href="https://validator.w3.org/check?uri=referer">Validate</a></p>
+</div>
+</body>
+</html>
diff --git a/2021-emacs-windows.org b/2021-emacs-windows.org
new file mode 100644
index 0000000..fea0f1e
--- /dev/null
+++ b/2021-emacs-windows.org
@@ -0,0 +1,97 @@
+#-*- mode: org -*-
+
+* Emacs and Learning to Live with Windows
+
+** Background/Preamble
+
+In May of 2021 I started a new job. On my first day of work I imaged my workstation with Fedora; I was coming into a
+sysadmin job in a primarily RHEL shop so this seemed appropriate. Upon getting my laptop I was informed that I could
+not install Linux on it -- VPN access was Windows only.
+
+ "OK, no problem", I thought to myself. I'm not a huge Windows fan, and I hadn't interacted with it meaningfully since
+probably the early 00's, but I figured how bad could it be?
+
+As it turns out -- not too bad. I was surprised to find there was some basic native window tiling behavior in the
+window manager, and with the release of the WSL and some flashy new windows terminal apps, I was pretty excited
+about how familiar it would feel.
+
+Unfortunately, I ran into a number of issues as I was exploring trying to get Windows to feel more Unix-y. I won't go into
+detail in this post (maybe another time), but I quickly discovered that there was a lot of muscle memory and UI workflows
+that just seemed unavailable to me in Windows (despite heroic community efforts to improve a lot of the Windows experience).
+
+** Enter Emacs
+
+Before starting this new job, I'd been a long time Vim user, but unrelated to this new job I'd started exploring Common Lisp
+programming, and as such had setup Emacs/SLIME. As part of that foray into Emacs/SLIME I'd discovered =eshell=, and as I was
+struggling to get Windows to conform to my preferred workflows I started to explore how I could use Emacs, elisp, and it's
+packages ecosystem to make my Windows experience more Unix-y.
+
+** The Beginning
+
+Initially I downloaded the Windows Emacs build and was pretty happy with the experience. I could use =eshell= to navigate
+the Windows file system in a familiar way, and had set up an [[https://orgmode.org/][Emacs Org mode file]] in my company OneDrive
+that I could easily update and track my work/notes in. When I was in the office on my Fedora workstation, I could easily update
+and keep notes in my Org file and then seamlessly access them on my laptop from home.
+
+The problems started arising when I wanted to do development for Linux systems on my Windows laptop, and easily be able
+to edit and quickly iterate.
+
+First, I tried setting up the WSL so that I could have a local Linux environment to do low stakes logic tests in. Unfortunately,
+the presence of a VPN tunnel seemed to cause a lot of problems for WSL and I couldn't get networking to work correctly
+in the WSL environment. This was kind of a non starter. I spent a decent amount of time trying to unravel it, but it quickly
+became a time sink that wasn't producing anything so I gave up.
+
+See here for more details on this problem: https://github.com/microsoft/WSL/issues/5068
+
+WSL not working, I tried using [[https://www.emacswiki.org/emacs/TrampMode][TRAMP]]. The idea was to just open files on my Linux workstation over
+SSH and then manage everything natively there using an SSH session. I had a number of issues that I couldn't trace down,
+but the biggest was that using the =plink= TRAMP method would indefinitely hang emacs on windows, forcing me to close it with the
+Windows task manager. As with above, had I spent a reasonable amount of time trying to debug this, I probably would've
+been able to figure out the error (which was probably a misconfiguration on my part), but as with above, it started to
+become a real time sink and I just wanted to get to work.
+
+Eventually, I seemed to figure out something that worked /beautifully/ for all of my expected cases.
+
+** Emacs Server Mode
+
+Emacs has a [[https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html][server mode]] that covered all my bases and allowed for all the flexibility I ended up needing.
+
+What I do is start a terminal emacs session in tmux with =emacs -nw= on my Linux workstation at the office.
+I can then do =M-x server-start= which will start the Emacs server. When I'm at home and working from my windows laptop,
+I have to use Emacs exclusively in terminal mode. This of course has some tradeoffs, but it surprisingly works very well,
+and even has great terminal mouse support (=M-x xterm-mouse-mode=). I can run any number of =emacsclient='s in tmux windows to easily manage and organize
+all my different development projects /AND/ I can access the state of any of the other sessions from whatever session I'm in, just
+using the native Emacs buffer functionality.
+
+Additionally, when I head into the office, I can seamlessly attach to the running Emacs server from GUI Emacs and pick up
+right where I left off.
+
+** Compromises and Other Thoughts
+
+There are a few obvious compromises with this setup.
+
+Firstly, I can't natively address the windows environment from my terminal, as Emacs is actually running on my Linux server. This however kind of
+turned out to be a non issue, because I'm never actually writing any software for Windows, or doing any work with it. I'm just forced to have it
+installed on my laptop.
+
+My sysadmin environment, for lack of a better term, has always been a large number of tmux sessions managing different
+aspects of the job. For example a tmux session for "$web Team Systems", a tmux session for "$app Team Systems", etc etc. By integrating my development environment
+into a similar tmux session, it allowed me easily hop in and out of different development contexts, regardless of which system I was using; just like
+with my "sysadmin environment".
+
+The immediate question that arises from this conclusion is: "Well, if you're just doing all your development in the terminal, why not just use Vim?"
+
+This question is not posed to restart the age old flame war, but considering that is exactly what I used to use, I should address it. The main reason is that,
+to my knowledge, I cannot run a Vim session in the terminal, and then "attach" to it with gvim (having all my tabs/files/etc open and available)
+when I come into the office and use the workstation locally.
+
+There are many Emacs features I've come to love, which I might cover another time, but this one feature has really got me stuck in Emacs (plus there is the
+famous [[https://github.com/emacs-evil/evil][EVIL mode]], which smooths over that transition quite a bit).
+
+To come back to the original point, the reason I no longer worry too much about the Windows experience is that through emacs+tmux+ssh, I don't really
+ever have to interact with Windows. It provides a basic interface to the web browser and to team communication, and virtually every other part of my
+job can be done over SSH in cygwin. In this way, I've kind of side stepped the purpose of this blog post -- I've just described how to use skirt
+actually using Windows as much as possible, as opposed to addressing solving these problems in a more Windows-centric way.
+
+The second major compromise here (I touched on it above) is that I end up using emacs as a terminal IDE far more often than I'd like. But given the choice between
+a very robust and functional development environment available over SSH and having to go into the office every day, it's a pretty easy trade for me.
diff --git a/2021-emacs-windows.pretty.html b/2021-emacs-windows.pretty.html
new file mode 100644
index 0000000..1786c02
--- /dev/null
+++ b/2021-emacs-windows.pretty.html
@@ -0,0 +1,222 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<!-- 2021-10-27 Wed 21:02 -->
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<title></title>
+<meta name="generator" content="Org mode" />
+<meta name="author" content="Simon Watson" />
+<style type="text/css">body{margin:40px
+auto;max-width:700px;line-height:1.6;font-size:18px;color:#444;padding:0
+10px}h1,h2,h3{line-height:1.2}</style>
+<script type="text/javascript">
+// @license magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=public-domain.txt Public Domain
+<!--/*--><![CDATA[/*><!--*/
+ function CodeHighlightOn(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.add("code-highlighted");
+ target.classList.add("code-highlighted");
+ }
+ }
+ function CodeHighlightOff(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.remove("code-highlighted");
+ target.classList.remove("code-highlighted");
+ }
+ }
+ /*]]>*///-->
+// @license-end
+</script>
+</head>
+<body>
+<div id="content">
+<div id="table-of-contents">
+<h2>Table of Contents</h2>
+<div id="text-table-of-contents">
+<ul>
+<li><a href="#orgd4831a0">1. Emacs and Learning to Live with Windows</a>
+<ul>
+<li><a href="#orgb4039ce">1.1. Background/Preamble</a></li>
+<li><a href="#orge44de3f">1.2. Enter Emacs</a></li>
+<li><a href="#org1ec967f">1.3. The Beginning</a></li>
+<li><a href="#org2f6f828">1.4. Emacs Server Mode</a></li>
+<li><a href="#orgf45ed4d">1.5. Compromises and Other Thoughts</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+<p>
+</p>
+
+<div id="outline-container-orgd4831a0" class="outline-2">
+<h2 id="orgd4831a0"><span class="section-number-2">1</span> Emacs and Learning to Live with Windows</h2>
+<div class="outline-text-2" id="text-1">
+</div>
+<div id="outline-container-orgb4039ce" class="outline-3">
+<h3 id="orgb4039ce"><span class="section-number-3">1.1</span> Background/Preamble</h3>
+<div class="outline-text-3" id="text-1-1">
+<p>
+In May of 2021 I started a new job. On my first day of work I imaged my workstation with Fedora; I was coming into a
+sysadmin job in a primarily RHEL shop so this seemed appropriate. Upon getting my laptop I was informed that I could
+not install Linux on it – VPN access was Windows only.
+</p>
+
+<p>
+ "OK, no problem", I thought to myself. I'm not a huge Windows fan, and I hadn't interacted with it meaningfully since
+probably the early 00's, but I figured how bad could it be?
+</p>
+
+<p>
+As it turns out – not too bad. I was surprised to find there was some basic native window tiling behavior in the
+window manager, and with the release of the WSL and some flashy new windows terminal apps, I was pretty excited
+about how familiar it would feel.
+</p>
+
+<p>
+Unfortunately, I ran into a number of issues as I was exploring trying to get Windows to feel more Unix-y. I won't go into
+detail in this post (maybe another time), but I quickly discovered that there was a lot of muscle memory and UI workflows
+that just seemed unavailable to me in Windows (despite heroic community efforts to improve a lot of the Windows experience).
+</p>
+</div>
+</div>
+
+<div id="outline-container-orge44de3f" class="outline-3">
+<h3 id="orge44de3f"><span class="section-number-3">1.2</span> Enter Emacs</h3>
+<div class="outline-text-3" id="text-1-2">
+<p>
+Before starting this new job, I'd been a long time Vim user, but unrelated to this new job I'd started exploring Common Lisp
+programming, and as such had setup Emacs/SLIME. As part of that foray into Emacs/SLIME I'd discovered <code>eshell</code>, and as I was
+struggling to get Windows to conform to my preferred workflows I started to explore how I could use Emacs, elisp, and it's
+packages ecosystem to make my Windows experience more Unix-y.
+</p>
+</div>
+</div>
+
+<div id="outline-container-org1ec967f" class="outline-3">
+<h3 id="org1ec967f"><span class="section-number-3">1.3</span> The Beginning</h3>
+<div class="outline-text-3" id="text-1-3">
+<p>
+Initially I downloaded the Windows Emacs build and was pretty happy with the experience. I could use <code>eshell</code> to navigate
+the Windows file system in a familiar way, and had set up an <a href="https://orgmode.org/">Emacs Org mode file</a> in my company OneDrive
+that I could easily update and track my work/notes in. When I was in the office on my Fedora workstation, I could easily update
+and keep notes in my Org file and then seamlessly access them on my laptop from home.
+</p>
+
+<p>
+The problems started arising when I wanted to do development for Linux systems on my Windows laptop, and easily be able
+to edit and quickly iterate.
+</p>
+
+<p>
+First, I tried setting up the WSL so that I could have a local Linux environment to do low stakes logic tests in. Unfortunately,
+the presence of a VPN tunnel seemed to cause a lot of problems for WSL and I couldn't get networking to work correctly
+in the WSL environment. This was kind of a non starter. I spent a decent amount of time trying to unravel it, but it quickly
+became a time sink that wasn't producing anything so I gave up.
+</p>
+
+<p>
+See here for more details on this problem: <a href="https://github.com/microsoft/WSL/issues/5068">https://github.com/microsoft/WSL/issues/5068</a>
+</p>
+
+<p>
+WSL not working, I tried using <a href="https://www.emacswiki.org/emacs/TrampMode">TRAMP</a>. The idea was to just open files on my Linux workstation over
+SSH and then manage everything natively there using an SSH session. I had a number of issues that I couldn't trace down,
+but the biggest was that using the <code>plink</code> TRAMP method would indefinitely hang emacs on windows, forcing me to close it with the
+Windows task manager. As with above, had I spent a reasonable amount of time trying to debug this, I probably would've
+been able to figure out the error (which was probably a misconfiguration on my part), but as with above, it started to
+become a real time sink and I just wanted to get to work.
+</p>
+
+<p>
+Eventually, I seemed to figure out something that worked <i>beautifully</i> for all of my expected cases.
+</p>
+</div>
+</div>
+
+<div id="outline-container-org2f6f828" class="outline-3">
+<h3 id="org2f6f828"><span class="section-number-3">1.4</span> Emacs Server Mode</h3>
+<div class="outline-text-3" id="text-1-4">
+<p>
+Emacs has a <a href="https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html">server mode</a> that covered all my bases and allowed for all the flexibility I ended up needing.
+</p>
+
+<p>
+What I do is start a terminal emacs session in tmux with <code>emacs -nw</code> on my Linux workstation at the office.
+I can then do <code>M-x server-start</code> which will start the Emacs server. When I'm at home and working from my windows laptop,
+I have to use Emacs exclusively in terminal mode. This of course has some tradeoffs, but it surprisingly works very well,
+and even has great terminal mouse support (<code>M-x xterm-mouse-mode</code>). I can run any number of <code>emacsclient</code>'s in tmux windows to easily manage and organize
+all my different development projects <i>AND</i> I can access the state of any of the other sessions from whatever session I'm in, just
+using the native Emacs buffer functionality.
+</p>
+
+<p>
+Additionally, when I head into the office, I can seamlessly attach to the running Emacs server from GUI Emacs and pick up
+right where I left off.
+</p>
+</div>
+</div>
+
+<div id="outline-container-orgf45ed4d" class="outline-3">
+<h3 id="orgf45ed4d"><span class="section-number-3">1.5</span> Compromises and Other Thoughts</h3>
+<div class="outline-text-3" id="text-1-5">
+<p>
+There are a few obvious compromises with this setup.
+</p>
+
+<p>
+Firstly, I can't natively address the windows environment from my terminal, as Emacs is actually running on my Linux server. This however kind of
+turned out to be a non issue, because I'm never actually writing any software for Windows, or doing any work with it. I'm just forced to have it
+installed on my laptop.
+</p>
+
+<p>
+My sysadmin environment, for lack of a better term, has always been a large number of tmux sessions managing different
+aspects of the job. For example a tmux session for "$web Team Systems", a tmux session for "$app Team Systems", etc etc. By integrating my development environment
+into a similar tmux session, it allowed me easily hop in and out of different development contexts, regardless of which system I was using; just like
+with my "sysadmin environment".
+</p>
+
+<p>
+The immediate question that arises from this conclusion is: "Well, if you're just doing all your development in the terminal, why not just use Vim?"
+</p>
+
+<p>
+This question is not posed to restart the age old flame war, but considering that is exactly what I used to use, I should address it. The main reason is that,
+to my knowledge, I cannot run a Vim session in the terminal, and then "attach" to it with gvim (having all my tabs/files/etc open and available)
+when I come into the office and use the workstation locally.
+</p>
+
+<p>
+There are many Emacs features I've come to love, which I might cover another time, but this one feature has really got me stuck in Emacs (plus there is the
+famous <a href="https://github.com/emacs-evil/evil">EVIL mode</a>, which smooths over that transition quite a bit).
+</p>
+
+<p>
+To come back to the original point, the reason I no longer worry too much about the Windows experience is that through emacs+tmux+ssh, I don't really
+ever have to interact with Windows. It provides a basic interface to the web browser and to team communication, and virtually every other part of my
+job can be done over SSH in cygwin. In this way, I've kind of side stepped the purpose of this blog post – I've just described how to use skirt
+actually using Windows as much as possible, as opposed to addressing solving these problems in a more Windows-centric way.
+</p>
+
+<p>
+The second major compromise here (I touched on it above) is that I end up using emacs as a terminal IDE far more often than I'd like. But given the choice between
+a very robust and functional development environment available over SSH and having to go into the office every day, it's a pretty easy trade for me.
+</p>
+</div>
+</div>
+</div>
+</div>
+<div id="postamble" class="status">
+<p class="author">Author: Simon Watson</p>
+<p class="date">Created: 2021-10-27 Wed 21:02</p>
+</div>
+</body>
+</html>
diff --git a/20210909-emacs.org b/20210909-emacs.org
deleted file mode 100644
index 53aa08c..0000000
--- a/20210909-emacs.org
+++ /dev/null
@@ -1,68 +0,0 @@
-#-*- mode: org -*-
-#TITLE: Emacs and Learning to Live with Windows
-
-** Background/Preamble
-
-In May of 2021 I started a new job. On my first day of work I imaged my workstation with Fedora; I was coming into a
-sysadmin job in a primarily RHEL shop so this seemed appropriate. Upon getting my laptop I was informed that I could
-not install Linux on it -- VPN access was Windows only.
-
- "OK, no problem", I thought to myself. I'm not a huge Windows fan, and I hadn't interacted with it meaningfully since
-probably the early 00's, but I figured how bad could it be?
-
-As it turns out -- not too bad. I was surprised to find there was some basic native window tiling behavior in the
-window manager, and with the release of the WSL and some flashy new windows terminal apps, I was pretty excited
-about how famaliar it would feel.
-
-Unfortunately, I ran into a number of issues as I was exploring trying to get Windows to feel more Unix-y. I won't go into
-detail in this post (maybe another time), but I quickly discovered that there was a lot of muscle memory and UI workflows
-that just seemed unavailable to me in Windows (despite heroic community efforts to improve a lot of the Windows experience).
-
-** Enter Emacs
-
-Before starting this new job, I'd been a long time Vim user, but unrelated to this new job I'd started exploring Common Lisp
-programming, and as such had setup Emacs/SLIME. As part of that foray into Emacs/SLIME I'd discovered =eshell=, and as I was
-struggling to get Windows to conform to my preferred workflows I started to explore how I could use Emacs, elisp, and it's
-packages ecosystem to make my Windows experience more Unix-y.
-
-** The Beginning
-
-Initially I downloaded the Windows Emacs build and was pretty happy with the experience. I could use =eshell= to navigate
-the Windows file system in a familiar way, and had set up an Emacs .org file[annotation/explaination here] in my company OneDrive
-that I could easily update and track my work/notes in. When I was in the office on my Fedora workstation, I could easily update
-and keep notes in my Org file and then seemlessly access them on my laptop from home.
-
-The problems started arising when I wanted to do development for Linux systems on my Windows laptop, and easily be able
-to edit and quickly iterate.
-
-First, I tried setting up the WSL so that I could have a local Linux environment to do low stakes logic tests in. Unfortunately,
-the presense of a VPN tunnel seemed to cause a lot of problems for WSL and I couldn't get networking to work correctly
-in the WSL environment. This was kind of a non starter. I spent a decent amount of time trying to unravel it, but it quickly
-became a time sink that wasn't producing anything so I gave up.
-
-See here for more details on this problem: https://github.com/microsoft/WSL/issues/5068
-
-WSL not working, I tried using TRAMP[annotation/link needed]. The idea was to just open files on my Linux workstation over
-SSH and then manage everything natively there using an SSH session. I had a number of issues that I couldn't trace down,
-but the biggest was that using the =plink= TRAMP method would indefinitely hang emacs on windows, forcing me to close it with the
-Windows task manager. As with above, had I spent a reasonable amount of time trying to debug this, I probably would've
-been able to figure out the error (which was probably a misconfiguration on my part), but as with above, it started to
-become a real time sink and I just wanted to get to work.
-
-Eventually, I seemed to figure out something that worked /beautifully/ for all of my expected cases.
-
-** Emacs Server Mode
-
-Emacs has a server mode[link to mode here] that covered all my bases and allowed for all the flexibility I ended up needing.
-
-What I do is start a terminal emacs session in tmux with =emacs -nw=. I can then do =M-x server-start= which will start the
-Emacs server. When I'm at home and working from my windows laptop, I have to use Emacs exclusively in terminal mode. This
-of course has some tradeoffs, but it surprisingly works very well, and even has great terminal mouse support[annotation for
-enabling terminal mouse support]. I can run any number of =emacsclient='s in tmux windows to easily manage and organize
-all my different development projects /AND/ I can access the state of any of the other sessions from that session.
-
-Additionally, when I head into the office, I can seamlessly attach to the running Emacs server from GUI Emacs and pick up
-right where I left off.
-
-
-