Alright!

content/blog/2026-05-12-deploying-evil-hl-line-and-highly-visual-indicators.org

@@ -1,19 +1,17 @@
 #+TITLE: Deploying evil-hl-line and highly visual indicators
 #+DATE: 2026-05-12
 
-* TLDR
+* TL;DR
 
-I created my first public Emacs package called =evil-hl-line= and it can be found on [[https://github.com/anerisgreat/evil-hl-line/][GitHub]]!
+I just released a public Emacs package, `evil-hl-line`, that adds a bright line‑highlight to indicate the current Evil state.  [[https://github.com/anerisgreat/evil-hl-line][GitHub]]
 
-* Why even make a package
+* Why I made this package
 
 I am an addicted evil-mode user. I mainlined vim (well, Neovim) and tmux for a year before switching to Emacs, so by the time I became enlightened I was set on using vim-style key bindings, and so I found myself to be an evil man.
 
-A problem I faced early on in my vim journey was mode confusion. You must always know which mode you are in, as this affects the key bindings you use. This makes perfect sense, but sometimes, you just forget. Especially if you have multiple windows open, and in each one, the mode might be different.
+Early on in my vim journey I kept hitting the wrong keys because I was not sure what mode I was in. The same continued to happen in Emacs with Evil mode. Especially with many windows open, constantly changing modes and pages and tabs means constantly forgetting which mode I am in, and pressing the wrong keys, resulting in unwated consequences. I would start typing thinking I am in insert mode, and accidentally delete a few paragraphs! The time these mistakes waste is annoying, but the most frustrating part is the drailement of my train of thought.
 
-I know this was a nuisance because of the amount of times I started pressing keys assuming I was in one mode but I found myself to be in another. Any vim/evil user has experienced this often at some point.
-
-Of course, there already exists visual indicator that tells us which mode is active. In Emacs, using evil mode introduces a little text inside the mode line that says what the current mode is (In vim such a thing exists too, of course). Yet I still found myself using the wrong mode often.
+Of course, there already exists visual indicator that tells us which mode is active. In Emacs, using evil mode introduces a little text inside the mode line that says what the current mode is (In vim such a thing exists too, of course). Even with these, I still found myself using the wrong mode often.
 
 * A fix - highly visual indicators
 
@@ -27,5 +25,3 @@ Knowing this, it seemed only natural to fix the mode confusion with a very obvio
 
 If you use evil mode in Emacs, I think you may find this approach helpful, and I hope you will find this package useful!
 
-
-

content/blog/2026-05-14-emacs-nix-org-config.org

@@ -1,19 +0,0 @@
-#+TITLE: Emacs + Nix + Org config
-#+DATE: 2026-05-14
-
-* Background for the uninitiated
-
-My personal workspace configuration is written in Nix nowadays (shocker), and the repo itself is about two years old.
-However, since I live in Emacs, most of the configuration lives in the =.org= files that define my Emacs experience, and these files have been through a few repos. Going back, I found the first commit of a config file that would later become what I use today. It is dated February 2020, so barely pre-covid.
-
-I currently have thousands of lines determining my Emacs experience, and so the use of ORG mode is really good for me. The configuration files themselves have thousands of lines of code. ORG mode configuration provides two key benefits:
-
-- Structure: with thousands of lines of code, it is easy to get lost. ORG mode makes navigating between levels and headings easy, allowing me to section off areas of the file for different aspects of the configuration.
-- Context: the ability to write also in plain English allows me to document oddities in the configuration very easily. This could be done with comments of course, but I find having the ability to write very readable English easily
-  makes me document more often.
-
-* Fast-forward to today
-
-Nowadays I have a NIX site.
-
-ur

flake.nix

@@ -62,7 +62,7 @@
           text = ''
             fuser -k 8080/tcp 2>/dev/null || true
             echo "Serving site at http://localhost:8080"
-            python -m http.server --bind 0.0.0.0 8080 -d ${site}
+            exec python -m http.server --bind 0.0.0.0 8080 -d ${site}
           '';
         };