emacs: update postHEADmaster

2 files changed, 27 insertions, 15 deletions

diff --git a/site/emacs.md b/site/emacs.md
index ca8ad05..d8e7ad3 100644
--- a/site/emacs.md
+++ b/site/emacs.md
@@ -1,14 +1,14 @@
-# Emacs
+# How I work in Emacs
 
-<time id="post-date">2025-01-29</time>
+<p class="subtitle">Posted on <time id="post-date">2025-01-29</time></p>
 
 <tags>draft, emacs</tags>
 
 <section>
 
 <p id="post-excerpt">
-You know what the world needs more of? Random internet pages where
-some dude writes about Emacs. So here's another one!
+This is about the way I use and work in Emacs, which I think departs
+from the more mainstream usage.
 </p>
 
 This is not so much about my Emacs setup. This is more about how I use
@@ -18,7 +18,22 @@ name="init.el">[init.el](https://git.sr.ht/~laumann/dotfiles/tree/master/item/em
 
 Generally, I try to keep my Emacs configuration as small as possible
 and leverage all the built-in functionality and this write-up is about
-recording all the things I find really useful in Emacs.
+recording all the things I find really useful in Emacs. I have tried
+configuration frameworks like Spacemacs<sidenote
+name="spacemacs"><https://www.spacemacs.org/></sidenote> and Doom
+Emacs<sidenote
+name="doom-emacs"><https://github.com/doomemacs/doomemacs></sidenote>,
+especially when I was switching back from Vim to Emacs. The issue I
+had with these configuration frameworks is that it adds another layer
+of things on top of vanilla Emacs that I need to know how to work
+with. <marginnote name="doom-discord">another reason for dropping Doom
+was the community living in Discord</marginnote>I really liked Doom
+Emacs and have cribbed some of the speed improvements, but I stopped
+using the framework. Today, my philosophy on Emacs configuration is
+more aligned with System Crafters<sidenote
+name="systemcrafters"><https://systemcrafters.net/></sidenote>, namely
+starting from vanilla Emacs, maintaining my own configuration and
+preferring built-in tools over external packages.
 
 </section><section>
 
@@ -49,10 +64,10 @@ rules! During development, I tend to follow this pattern:
  1. Set up a command with <kbd>M-x compile</kbd>. For example `make` or `dune
 build` or `dune build && ./run-tests`
 
- 2. <marginnote name="good-output">this only works if the compiler
-produces error output with file names and line numbers</marginnote>If
-there is an error in the output, it's nicely highlighted and <kbd>M-g n</kbd>
-takes me directly to the file and line with an error.
+ 2. If there is an error in the output, it's nicely highlighted and
+<kbd>M-g n</kbd> takes me directly to the file and line with an
+error. (This only works if the compiler produces error output with
+file names and line numbers.)
 
  3. <kbd>F9</kbd> is set up as a shortcut for <kbd>M-x recompile</kbd>, so repeating the
     command is just one keystroke
@@ -108,7 +123,8 @@ because it's supposedly great. I tried and found it difficult to
 navigate and remember all the shortcuts. I also suffer from fat finger
 syndrome and many times experienced hitting some random key that
 turned out to be bound to a Magit function, then the UI changed and I
-was immediately lost.
+was immediately lost. The only part of Magit that I use (and like) is
+the git-commit package.
 
 Mostly I found that the terminology used in Magit is just slightly off
 from Git's own and that causes me a lot of confusion. Plus the
diff --git a/site/extra.css b/site/extra.css
index f38a42e..891855e 100644
--- a/site/extra.css
+++ b/site/extra.css
@@ -36,9 +36,5 @@ kbd {
     border: 1px solid #aaa;
     background-color: #fff;
     padding: 2px 5px;
-    /* box-shadow: 0 2px 0 1px #777; */
-    /* line-height: 1; */
-    /* /\* display: block; *\/ */
-    /* position: relative; */
-    /* top: -1px; */
+    white-space: nowrap;
 }