commit d1da0f2afea800478c61472f96299a2cb5b62bab
Author: U-IPC_NAMERICA\watsonsi <watsonsi@WATSONSI-L5400.corp.root.ipc.com>
Date:   Tue Oct 19 10:13:18 2021 -0400

    More stuff

diff --git a/20210909-emacs.org b/20210909-emacs.org
index b7e62b3..53aa08c 100644
--- a/20210909-emacs.org
+++ b/20210909-emacs.org
@@ -1,5 +1,5 @@
 #-*- mode: org -*-
-#TITLE: My Emacs Workflow (and other ramblings)
+#TITLE: Emacs and Learning to Live with Windows
 
 ** Background/Preamble
 
@@ -25,9 +25,44 @@ programming, and as such had setup Emacs/SLIME. As part of that foray into Emacs
 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.
 
-** Emacs Workflow 1
+** 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 in my company OneDrive that I could
-easily update and track my work/notes in.
+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.
+
+