Update content for gemtext

4 files changed, 314 insertions, 1 deletions

diff --git a/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi b/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi
new file mode 100644
index 00000000..f3294363
--- /dev/null
+++ b/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi
@@ -0,0 +1,170 @@
+# I tried Doom Emacs, but I switched back to (Neo)Vim
+
+> Published by Paul at 2021-11-24
+
+As a long-lasting user of Vim (and NeoVim), I always wondered what GNU Emacs is really about, so I decided to try it. I didn't try vanilla GNU Emacs, but Doom Emacs. I chose Doom Emacs as it is a neat distribution of Emacs with Evil mode enabled by default. Evil mode allows Vi(m) key bindings (so to speak, it's emulating Vim within Emacs), and I am pretty sure I won't be ready to give up all the muscle memory I have built over more than a decade.
+
+=> https://www.gnu.org/software/emacs/ GNU Emacs
+=> https://github.com/doomemacs/ Doom Emacs
+
+I used Doom Emacs for around two months. Still, ultimately I decided to switch back to NeoVim as my primary editor and IDE and Vim (usually pre-installed on Linux-based systems) and Nvi (usually pre-installed on *BSD systems) as my "always available editor" for quick edits. (It is worth mentioning that I don't have a high opinion on whether Vim or NeoVim is the better editor, I prefer NeoVim as it comes with better defaults out of the box, but there is no real blocker to use Vim instead).
+
+=> https://www.vim.org Vim
+=> https://neovim.io NeoVim
+
+So why did I switch back to the Vi-family?
+
+## Emacs is a giant dragon
+
+Emacs feels like a giant dragon as it is much more than an editor or an integrated development environment. Emacs is a whole platform on its own. There's an E-Mail client, an IRC client, or even games you can run within Emacs. And you can also change Emacs within Emacs using its own Lisp dialect, Emacs Lisp (Emacs is programmed in Emacs Lisp). Therefore, Emacs is also its own programming language. You can change every aspect of Emacs within Emacs itself. People jokingly state Emacs is an operating system and that you should directly use it as the `init 1` process (if you don't know what the `init 1` process is: Under UNIX and similar operating systems, it's the very first userland processed launched. That's usually `systemd` on Linux-based systems, `launchd` on macOS, or any other init script or init system used by the OS)!
+
+In many aspects, Emacs is like shooting at everything with a bazooka! However, I prefer it simple. I only wanted Emacs to be a good editor (which it is, too), but there's too much other stuff in Emacs that I don't need to care about! Vim and NeoVim do one thing excellent: Being great text editors and, when loaded with plugins, decent IDEs, too. 
+
+## Magit love
+
+I almost fell in love with Magit, an integrated Git client for Emacs. But I think the best way to interact with Git is to use the `git` command line directly. I don't worry about typing out all the commands, as the most commonly used commands are in my shell history. Other useful Git programs I use frequently are `bit` and `tig`. Also, get a mechanical keyboard that makes hammering whole commands into the terminal even more enjoyable.
+
+=> https://magit.vc/ Magit
+=> https://github.com/jonas/tig Tig
+
+Magit is pretty neat for basic Git operations, but I found myself searching the internet for the correct sub-commands to do the things I wanted to do in Git. Mainly, the way how branches are managed is confusing. Often, I fell back to the command line to fix up the mess I produced with Magit (e.g. accidentally pushing to the wrong remote branch, so I found myself fixing things manually on the terminal with the `git` command with forced pushes....). Magit is hotkey driven, and common commands are quickly explorable through built-in hotkey menus. Still, I found it challenging to navigate to more advanced Git sub-commands that way which was much easier accomplished by using the `git` command directly.
+
+## Graphical UI
+
+If there is one thing I envy about Emacs is that it's a graphical program, whereas the Vi-family of editors are purely terminal-based. I see the benefits of being a graphical program as this enables the use of multiple fonts simultaneously to embed pictures and graphs (that would be neat as a Markdown preview, for example). There's also GVim (Vim with GTK UI), but that's more of an afterthought.
+
+There are now graphical front-end clients for NeoVim, but I still need to dig into them. Let me know your experience if you have one. Luckily, I don't rely on something graphical in my text editor, but it would improve how the editor looks and feels. UTF8 can already do a lot in the terminal, and terminal emulators also allow you to use TrueType fonts. Still, you will always be limited to one TTF font for the whole terminal, and it isn't possible to have, for example, a different font for headings, paragraphs, etc... you get the idea. TTF+UTF8 can't beat authentic graphics. 
+
+## Scripting it
+
+It is possible to customize every aspect of Emacs through Emacs Lisp. I have done some Elk Scheme programming in the past (a dialect of Lisp), but that was a long time ago, and I am not willing to dive here again to customize my environment. I would instead take the pragmatic approach and script what I need in VimScript (a terrible language, but it gets the job done!). I watched Damian Conway's VimScript course on O'Reilly Safari Books Online, which I greatly recommend. Yes, VimScript feels clunky, funky and weird and is far less elegant than Lisp, but it gets its job done - in most cases! (That reminds me that the Vim team has announced a new major version of VimScript with improvements and language changes made - I haven't gotten to it yet - but I assume that VimScript will always stay VimScript).
+
+=> https://en.wikipedia.org/wiki/Emacs_Lisp Emacs Lisp
+=> http://sam.zoy.org/elk/ Elk Scheme
+=> http://vimscript.org/ VimScript
+=> https://www.oreilly.com/library/view/scripting-vim/9781491996287/ Scripting Vim by Damian Conway
+
+NeoVim is also programmable with Lua, which seems to be a step up and Vim comes with a Perl plugin API (which was removed from NeoVim, but that is a different story - why would someone remove the most potent mature text manipulation programming language from one of the most powerful text editors?).
+
+=> https://neovim.io/doc/user/lua.html NeoVim Lua API
+
+One example is my workflow of how I compose my blog articles (e.g. this one you are currently reading): I am writing everything in NeoVim, but I also want to have every paragraph checked against Grammarly (as English is not my first language). So I write a whole paragraph, then I select the entire paragraph via visual selection with `SHIFT+v`, and then I press `,y` to yank the paragraph to the systems clipboard, then I paste the paragraph to Grammarly's browser window with `CTRL+v`, let Grammarly suggest the improvements, and then I copy the result back with `CTRL+c` to the system clipboard and in NeoVim I type `,i` to insert the result back overriding the old paragraph (which is still selected in visual mode) with the new content. That all sounds a bit complicated, but it's surprisingly natural and efficient.
+
+To come back to the example, for the clipboard integration, I use this small VimScript snippet, and I didn't have to dig into any Lisp or Perl for this:
+
+```
+" Clipboard
+
+if uname != 'Darwin'
+  vnoremap ,y !gpaste-client<CR>ugv
+  vnoremap ,i !gpaste-client --use-index get 0<CR>
+  nmap ,i !wgpaste-client --use-index get 0<CR>
+else
+  vnoremap ,y !pbcopy<CR>ugv
+  vnoremap ,i !pbpaste<CR>
+  nmap ,i !wpbpaste<CR>
+endif
+```
+
+That's only a very few lines and does precisely what I want. It's quick and dirty but get's the job done! If VimScript becomes too cumbersome, I can use Lua for NeoVim scripting.
+
+## The famous Emacs Org mode
+
+Org-mode is an Emacs mode for keeping notes, authoring documents, computational notebooks, literate programming, maintaining to-do lists, planning projects, and more — in a fast and effective plain-text system. There's even a dedicated website for it:
+
+=> https://orgmode.org/
+
+In short, Org-mode is an "interactive markup language" that helps you organize everything mentioned above. I rarely touched the surface during my two-month experiment with Emacs, and I am impressed by it, so I see the benefits of having that. But it's not for me.
+
+I use "Dead Paper Mode" to organize my work and notes. Dead paper? Yeah, I use an actual pen and a real paper journal (Leuchtturm or a Moleskine and a set of coloured `0.5` Muji Pens are excellent choices). That's far more immersive and flexible than a computer program can ever be. Yes, some automation and interaction with the computer (like calendar scheduling etc.) are missing. Still, an actual paper journal forces you to stay simple and focus on the actual work rather than tinkering with your computer program. (But I could not resist, and I wrote a VimScript which parses a table of contents page in Markdown format of my scanned paper journals, and NeoVim allows me to select a topic so that the corresponding PDF scan on the right journal page gets opened in an external PDF viewer (the PDF viewer is `zathura`, it uses Vi-keybindings, of course) :-). (See the appendix of this blog post for that script).
+
+=> https://pwmt.org/projects/zathura/ Zathura
+
+On the road, I also write some of my notes in Markdown format to NextCloud Notes, which is editable from my phone and via NeoVim on my computers. Markdown is much less powerful than Org-mode, but I prefer it the simple way. There's a neat terminal application, `ranger,` which I use to browse my NextCloud Notes when they are synced to a local folder on my machine. `ranger` is a file manager inspired by Vim and therefore makes use of Vim keybindings and it feels just natural to me. 
+
+=> https://github.com/ranger/ranger Ranger - A Vim inspired file manager
+Did I mention that I also use my `zsh` (my default shell) and my `tmux` (terminal multiplexer) in Vi-mode?
+
+=> https://zsh.sourceforge.io/ Z shell
+=> https://github.com/tmux/tmux tmux terminal multiplexer
+
+## Seeking simplicity
+
+I am not ready to dive deep into the whole world of Emacs. I prefer small and simple tools as opposed to complex tools. Emacs comes with many features out of the box, whereas in Vim/NeoVim, you would need to install many plugins to replicate some of the behaviour. Yes, I need to invest time managing all the Vim/NeoVim plugins I use, but I feel more in control compared to Doom Emacs, where a framework around vanilla Emacs manages all the plugins. I could use vanilla Emacs and manage all my plugins the vanilla way, but for me, it's not worth the effort to learn and dive into that as all that I want to do I can already do with Vim/NeoVim.
+
+I am not saying that Vim/NeoVim are simple programs, but they are much simpler than Emacs with much smaller footprints; furthermore, they appear to be more straightforward as I am used to them. I only need Vim/NeoVim to be an editor, an IDE (through some plugins), and nothing more.
+
+## Conclusion
+
+I understand the Emacs users now. Emacs is an incredibly powerful platform for almost everything, not just text editing. With Emacs, you can do nearly everything (Writing, editing, programming, calendar scheduling and note taking, Jira integration, playing games, reading/writing emails, browsing the web, using as a calculator, generating HTML pages, configuring interactive menus, jumping around between every feature and every file within one single session, chat on IRC, surf the Gopherspace, ... the options are endless....). If you want to have one piece of software which rules it all and you are happy to invest a large part of your time in your platform: Pick Emacs, and over time Emacs will become "your" Emacs, customized to your own needs and change the way it works, which makes the Emacs users stick even more to it.
+
+Vim/NeoVim also comes with a very high degree of customization options, but to a lesser extreme than Emacs (but still, a much higher degree than most other editors out there). If you want the best text editor in the world, which can also be tweaked to be a decent IDE, you are only looking for: Pick Vim or NeoVim! You would also need to invest a lot of time in learning, tweaking and customizing Vim/NeoVim, but that's a little more straightforward, and the result is much more lightweight once you get used to the "Vi way of doing things" you never would want to change back. I haven't tried the Emacs vanilla keystrokes, but they are terrible (that's probably one of the reasons why Doom Emacs uses Vim keybindings by default).
+
+E-Mail your comments to paul at buetow dot org! :-)
+
+=> ../ Go back to the main site
+
+# Appendinx
+
+This is the VimScript I mentioned earlier, which parses a table of contents index of my scanned paper journals and opens the corresponding PDF at the right page in an external PDF editor:
+
+```
+function! ReadJournalPageNumber()
+    let page = expand("<cword>")
+    if page !~# '^\d\+$'
+        for str in split(getline("."), "[ ,]")
+            if str =~# '^\d\+$'
+                let page = str
+                break
+            end
+        endfor
+    endif
+    return page
+endfunction
+
+function! ReadJournalMeta()
+    normal! mj
+
+    1/MetaFilePath:/
+    normal! 3w
+    let s:metaFilePath = expand("<cWORD>")
+    echom s:metaFilePath
+
+    1/MetaOffset:/
+    normal! 3w
+    let s:metaOffset = expand("<cword>")
+    echom s:metaOffset
+
+    1/MetaPageAtOffset:/
+    normal! 3w
+    let s:metaPageAtOffset = expand("<cword>")
+    echom s:metaPageAtOffset
+
+    1/MetaPagesPerScan:/
+    normal! 3w
+    let s:metaPagesPerScan = expand("<cword>")
+    echom s:metaPagesPerScan
+
+    normal! `j
+endfunction
+
+function! GetPdfPage(page)
+    return s:metaOffset + (a:page - s:metaPageAtOffset) / s:metaPagesPerScan
+endfunction
+
+function! OpenJournalPage()
+    let page = ReadJournalPageNumber()
+    if page !~# '^\d\+$'
+        echoerr "Could not identify Journal page number"
+    end
+    call ReadJournalMeta()
+    let pdfPage = GetPdfPage(page)
+    echon "Location is " . s:metaFilePath . ":" . pdfPage
+    call system("zathura --mode fullscreen -P " . pdfPage . " " . s:metaFilePath)
+    " call system("evince -p " . pdfPage . " " . s:metaFilePath)
+endfunction
+
+nmap ,j :call OpenJournalPage()<CR>
+```
+
+=> ../ Go back to the main site
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index cdb6b4ce..396da45b 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,12 +1,153 @@
 <?xml version="1.0" encoding="utf-8"?>
 <feed xmlns="http://www.w3.org/2005/Atom">
-    <updated>2022-11-23T22:35:52+02:00</updated>
+    <updated>2022-11-24T11:36:26+02:00</updated>
     <title>foo.zone feed</title>
     <subtitle>To be in the .zone!</subtitle>
     <link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" />
     <link href="gemini://foo.zone/" />
     <id>gemini://foo.zone/</id>
     <entry>
+        <title>I tried Doom Emacs, but I switched back to (Neo)Vim</title>
+        <link href="gemini://foo.zone/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi" />
+        <id>gemini://foo.zone/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi</id>
+        <updated>2022-11-24T11:17:15+02:00</updated>
+        <author>
+            <name>Paul C. Buetow</name>
+            <email>comments@mx.buetow.org</email>
+        </author>
+        <summary>As a long-lasting user of Vim (and NeoVim), I always wondered what GNU Emacs is really about, so I decided to try it. I didn't try vanilla GNU Emacs, but Doom Emacs. I chose Doom Emacs as it is a neat distribution of Emacs with Evil mode enabled by default. Evil mode allows Vi(m) key bindings (so to speak, it's emulating Vim within Emacs), and I am pretty sure I won't be ready to give up all the muscle memory I have built over more than a decade.. .....to read on please visit my site.</summary>
+        <content type="xhtml">
+            <div xmlns="http://www.w3.org/1999/xhtml">
+                1c1
+< -rw-r--r--. 1 paul paul 13961 Nov 24 11:33 ../foo.zone-content/gemtext/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi
+---
+> -rw-r--r--. 1 paul paul 14073 Nov 24 11:35 ../foo.zone-content/gemtext/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi
+<h1>I tried Doom Emacs, but I switched back to (Neo)Vim</h1>
+<p class="quote"><i>Published by Paul at 2021-11-24</i></p>
+<p>As a long-lasting user of Vim (and NeoVim), I always wondered what GNU Emacs is really about, so I decided to try it. I didn't try vanilla GNU Emacs, but Doom Emacs. I chose Doom Emacs as it is a neat distribution of Emacs with Evil mode enabled by default. Evil mode allows Vi(m) key bindings (so to speak, it's emulating Vim within Emacs), and I am pretty sure I won't be ready to give up all the muscle memory I have built over more than a decade.</p>
+<a class="textlink" href="https://www.gnu.org/software/emacs/">GNU Emacs</a><br />
+<a class="textlink" href="https://github.com/doomemacs/">Doom Emacs</a><br />
+<p>I used Doom Emacs for around two months. Still, ultimately I decided to switch back to NeoVim as my primary editor and IDE and Vim (usually pre-installed on Linux-based systems) and Nvi (usually pre-installed on *BSD systems) as my "always available editor" for quick edits. (It is worth mentioning that I don't have a high opinion on whether Vim or NeoVim is the better editor, I prefer NeoVim as it comes with better defaults out of the box, but there is no real blocker to use Vim instead).</p>
+<a class="textlink" href="https://www.vim.org">Vim</a><br />
+<a class="textlink" href="https://neovim.io">NeoVim</a><br />
+<p>So why did I switch back to the Vi-family?</p>
+<h2>Emacs is a giant dragon</h2>
+<p>Emacs feels like a giant dragon as it is much more than an editor or an integrated development environment. Emacs is a whole platform on its own. There's an E-Mail client, an IRC client, or even games you can run within Emacs. And you can also change Emacs within Emacs using its own Lisp dialect, Emacs Lisp (Emacs is programmed in Emacs Lisp). Therefore, Emacs is also its own programming language. You can change every aspect of Emacs within Emacs itself. People jokingly state Emacs is an operating system and that you should directly use it as the <span class="inlinecode">init 1</span> process (if you don't know what the <span class="inlinecode">init 1</span> process is: Under UNIX and similar operating systems, it's the very first userland processed launched. That's usually <span class="inlinecode">systemd</span> on Linux-based systems, <span class="inlinecode">launchd</span> on macOS, or any other init script or init system used by the OS)!</p>
+<p>In many aspects, Emacs is like shooting at everything with a bazooka! However, I prefer it simple. I only wanted Emacs to be a good editor (which it is, too), but there's too much other stuff in Emacs that I don't need to care about! Vim and NeoVim do one thing excellent: Being great text editors and, when loaded with plugins, decent IDEs, too. </p>
+<h2>Magit love</h2>
+<p>I almost fell in love with Magit, an integrated Git client for Emacs. But I think the best way to interact with Git is to use the <span class="inlinecode">git</span> command line directly. I don't worry about typing out all the commands, as the most commonly used commands are in my shell history. Other useful Git programs I use frequently are <span class="inlinecode">bit</span> and <span class="inlinecode">tig</span>. Also, get a mechanical keyboard that makes hammering whole commands into the terminal even more enjoyable.</p>
+<a class="textlink" href="https://magit.vc/">Magit</a><br />
+<a class="textlink" href="https://github.com/jonas/tig">Tig</a><br />
+<p>Magit is pretty neat for basic Git operations, but I found myself searching the internet for the correct sub-commands to do the things I wanted to do in Git. Mainly, the way how branches are managed is confusing. Often, I fell back to the command line to fix up the mess I produced with Magit (e.g. accidentally pushing to the wrong remote branch, so I found myself fixing things manually on the terminal with the <span class="inlinecode">git</span> command with forced pushes....). Magit is hotkey driven, and common commands are quickly explorable through built-in hotkey menus. Still, I found it challenging to navigate to more advanced Git sub-commands that way which was much easier accomplished by using the <span class="inlinecode">git</span> command directly.</p>
+<h2>Graphical UI</h2>
+<p>If there is one thing I envy about Emacs is that it's a graphical program, whereas the Vi-family of editors are purely terminal-based. I see the benefits of being a graphical program as this enables the use of multiple fonts simultaneously to embed pictures and graphs (that would be neat as a Markdown preview, for example). There's also GVim (Vim with GTK UI), but that's more of an afterthought.</p>
+<p>There are now graphical front-end clients for NeoVim, but I still need to dig into them. Let me know your experience if you have one. Luckily, I don't rely on something graphical in my text editor, but it would improve how the editor looks and feels. UTF8 can already do a lot in the terminal, and terminal emulators also allow you to use TrueType fonts. Still, you will always be limited to one TTF font for the whole terminal, and it isn't possible to have, for example, a different font for headings, paragraphs, etc... you get the idea. TTF+UTF8 can't beat authentic graphics. </p>
+<h2>Scripting it</h2>
+<p>It is possible to customize every aspect of Emacs through Emacs Lisp. I have done some Elk Scheme programming in the past (a dialect of Lisp), but that was a long time ago, and I am not willing to dive here again to customize my environment. I would instead take the pragmatic approach and script what I need in VimScript (a terrible language, but it gets the job done!). I watched Damian Conway's VimScript course on O'Reilly Safari Books Online, which I greatly recommend. Yes, VimScript feels clunky, funky and weird and is far less elegant than Lisp, but it gets its job done - in most cases! (That reminds me that the Vim team has announced a new major version of VimScript with improvements and language changes made - I haven't gotten to it yet - but I assume that VimScript will always stay VimScript).</p>
+<a class="textlink" href="https://en.wikipedia.org/wiki/Emacs_Lisp">Emacs Lisp</a><br />
+<a class="textlink" href="http://sam.zoy.org/elk/">Elk Scheme</a><br />
+<a class="textlink" href="http://vimscript.org/">VimScript</a><br />
+<a class="textlink" href="https://www.oreilly.com/library/view/scripting-vim/9781491996287/">Scripting Vim by Damian Conway</a><br />
+<p>NeoVim is also programmable with Lua, which seems to be a step up and Vim comes with a Perl plugin API (which was removed from NeoVim, but that is a different story - why would someone remove the most potent mature text manipulation programming language from one of the most powerful text editors?).</p>
+<a class="textlink" href="https://neovim.io/doc/user/lua.html">NeoVim Lua API</a><br />
+<p>One example is my workflow of how I compose my blog articles (e.g. this one you are currently reading): I am writing everything in NeoVim, but I also want to have every paragraph checked against Grammarly (as English is not my first language). So I write a whole paragraph, then I select the entire paragraph via visual selection with <span class="inlinecode">SHIFT+v</span>, and then I press <span class="inlinecode">,y</span> to yank the paragraph to the systems clipboard, then I paste the paragraph to Grammarly's browser window with <span class="inlinecode">CTRL+v</span>, let Grammarly suggest the improvements, and then I copy the result back with <span class="inlinecode">CTRL+c</span> to the system clipboard and in NeoVim I type <span class="inlinecode">,i</span> to insert the result back overriding the old paragraph (which is still selected in visual mode) with the new content. That all sounds a bit complicated, but it's surprisingly natural and efficient.</p>
+<p>To come back to the example, for the clipboard integration, I use this small VimScript snippet, and I didn't have to dig into any Lisp or Perl for this:</p>
+<pre>
+" Clipboard
+
+if uname != 'Darwin'
+  vnoremap ,y !gpaste-client&lt;CR&gt;ugv
+  vnoremap ,i !gpaste-client --use-index get 0&lt;CR&gt;
+  nmap ,i !wgpaste-client --use-index get 0&lt;CR&gt;
+else
+  vnoremap ,y !pbcopy&lt;CR&gt;ugv
+  vnoremap ,i !pbpaste&lt;CR&gt;
+  nmap ,i !wpbpaste&lt;CR&gt;
+endif
+</pre><br />
+<p>That's only a very few lines and does precisely what I want. It's quick and dirty but get's the job done! If VimScript becomes too cumbersome, I can use Lua for NeoVim scripting.</p>
+<h2>The famous Emacs Org mode</h2>
+<p>Org-mode is an Emacs mode for keeping notes, authoring documents, computational notebooks, literate programming, maintaining to-do lists, planning projects, and more — in a fast and effective plain-text system. There's even a dedicated website for it:</p>
+<a class="textlink" href="https://orgmode.org/">https://orgmode.org/</a><br />
+<p>In short, Org-mode is an "interactive markup language" that helps you organize everything mentioned above. I rarely touched the surface during my two-month experiment with Emacs, and I am impressed by it, so I see the benefits of having that. But it's not for me.</p>
+<p>I use "Dead Paper Mode" to organize my work and notes. Dead paper? Yeah, I use an actual pen and a real paper journal (Leuchtturm or a Moleskine and a set of coloured <span class="inlinecode">0.5</span> Muji Pens are excellent choices). That's far more immersive and flexible than a computer program can ever be. Yes, some automation and interaction with the computer (like calendar scheduling etc.) are missing. Still, an actual paper journal forces you to stay simple and focus on the actual work rather than tinkering with your computer program. (But I could not resist, and I wrote a VimScript which parses a table of contents page in Markdown format of my scanned paper journals, and NeoVim allows me to select a topic so that the corresponding PDF scan on the right journal page gets opened in an external PDF viewer (the PDF viewer is <span class="inlinecode">zathura</span>, it uses Vi-keybindings, of course) :-). (See the appendix of this blog post for that script).</p>
+<a class="textlink" href="https://pwmt.org/projects/zathura/">Zathura</a><br />
+<p>On the road, I also write some of my notes in Markdown format to NextCloud Notes, which is editable from my phone and via NeoVim on my computers. Markdown is much less powerful than Org-mode, but I prefer it the simple way. There's a neat terminal application, <span class="inlinecode">ranger,</span> which I use to browse my NextCloud Notes when they are synced to a local folder on my machine. <span class="inlinecode">ranger</span> is a file manager inspired by Vim and therefore makes use of Vim keybindings and it feels just natural to me. </p>
+<a class="textlink" href="https://github.com/ranger/ranger">Ranger - A Vim inspired file manager</a><br />
+<p>Did I mention that I also use my <span class="inlinecode">zsh</span> (my default shell) and my <span class="inlinecode">tmux</span> (terminal multiplexer) in Vi-mode?</p>
+<a class="textlink" href="https://zsh.sourceforge.io/">Z shell</a><br />
+<a class="textlink" href="https://github.com/tmux/tmux">tmux terminal multiplexer</a><br />
+<h2>Seeking simplicity</h2>
+<p>I am not ready to dive deep into the whole world of Emacs. I prefer small and simple tools as opposed to complex tools. Emacs comes with many features out of the box, whereas in Vim/NeoVim, you would need to install many plugins to replicate some of the behaviour. Yes, I need to invest time managing all the Vim/NeoVim plugins I use, but I feel more in control compared to Doom Emacs, where a framework around vanilla Emacs manages all the plugins. I could use vanilla Emacs and manage all my plugins the vanilla way, but for me, it's not worth the effort to learn and dive into that as all that I want to do I can already do with Vim/NeoVim.</p>
+<p>I am not saying that Vim/NeoVim are simple programs, but they are much simpler than Emacs with much smaller footprints; furthermore, they appear to be more straightforward as I am used to them. I only need Vim/NeoVim to be an editor, an IDE (through some plugins), and nothing more.</p>
+<h2>Conclusion</h2>
+<p>I understand the Emacs users now. Emacs is an incredibly powerful platform for almost everything, not just text editing. With Emacs, you can do nearly everything (Writing, editing, programming, calendar scheduling and note taking, Jira integration, playing games, reading/writing emails, browsing the web, using as a calculator, generating HTML pages, configuring interactive menus, jumping around between every feature and every file within one single session, chat on IRC, surf the Gopherspace, ... the options are endless....). If you want to have one piece of software which rules it all and you are happy to invest a large part of your time in your platform: Pick Emacs, and over time Emacs will become "your" Emacs, customized to your own needs and change the way it works, which makes the Emacs users stick even more to it.</p>
+<p>Vim/NeoVim also comes with a very high degree of customization options, but to a lesser extreme than Emacs (but still, a much higher degree than most other editors out there). If you want the best text editor in the world, which can also be tweaked to be a decent IDE, you are only looking for: Pick Vim or NeoVim! You would also need to invest a lot of time in learning, tweaking and customizing Vim/NeoVim, but that's a little more straightforward, and the result is much more lightweight once you get used to the "Vi way of doing things" you never would want to change back. I haven't tried the Emacs vanilla keystrokes, but they are terrible (that's probably one of the reasons why Doom Emacs uses Vim keybindings by default).</p>
+<p>E-Mail your comments to paul at buetow dot org! :-)</p>
+<h1>Appendinx</h1>
+<p>This is the VimScript I mentioned earlier, which parses a table of contents index of my scanned paper journals and opens the corresponding PDF at the right page in an external PDF editor:</p>
+<pre>
+function! ReadJournalPageNumber()
+    let page = expand("&lt;cword&gt;")
+    if page !~# '^\d\+$'
+        for str in split(getline("."), "[ ,]")
+            if str =~# '^\d\+$'
+                let page = str
+                break
+            end
+        endfor
+    endif
+    return page
+endfunction
+
+function! ReadJournalMeta()
+    normal! mj
+
+    1/MetaFilePath:/
+    normal! 3w
+    let s:metaFilePath = expand("&lt;cWORD&gt;")
+    echom s:metaFilePath
+
+    1/MetaOffset:/
+    normal! 3w
+    let s:metaOffset = expand("&lt;cword&gt;")
+    echom s:metaOffset
+
+    1/MetaPageAtOffset:/
+    normal! 3w
+    let s:metaPageAtOffset = expand("&lt;cword&gt;")
+    echom s:metaPageAtOffset
+
+    1/MetaPagesPerScan:/
+    normal! 3w
+    let s:metaPagesPerScan = expand("&lt;cword&gt;")
+    echom s:metaPagesPerScan
+
+    normal! `j
+endfunction
+
+function! GetPdfPage(page)
+    return s:metaOffset + (a:page - s:metaPageAtOffset) / s:metaPagesPerScan
+endfunction
+
+function! OpenJournalPage()
+    let page = ReadJournalPageNumber()
+    if page !~# '^\d\+$'
+        echoerr "Could not identify Journal page number"
+    end
+    call ReadJournalMeta()
+    let pdfPage = GetPdfPage(page)
+    echon "Location is " . s:metaFilePath . ":" . pdfPage
+    call system("zathura --mode fullscreen -P " . pdfPage . " " . s:metaFilePath)
+    " call system("evince -p " . pdfPage . " " . s:metaFilePath)
+endfunction
+
+nmap ,j :call OpenJournalPage()&lt;CR&gt;
+</pre><br />
+            </div>
+        </content>
+    </entry>
+    <entry>
         <title>Installing DTail on OpenBSD</title>
         <link href="gemini://foo.zone/gemfeed/2022-10-30-installing-dtail-on-openbsd.gmi" />
         <id>gemini://foo.zone/gemfeed/2022-10-30-installing-dtail-on-openbsd.gmi</id>
diff --git a/gemfeed/index.gmi b/gemfeed/index.gmi
index e52eebeb..8540933a 100644
--- a/gemfeed/index.gmi
+++ b/gemfeed/index.gmi
@@ -2,6 +2,7 @@
 
 ## To be in the .zone!
 
+=> ./2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi 2022-11-24 - I tried Doom Emacs, but I switched back to (Neo)Vim
 => ./2022-10-30-installing-dtail-on-openbsd.gmi 2022-10-30 - Installing DTail on OpenBSD
 => ./2022-09-30-after-a-bad-nights-sleep.gmi 2022-09-30 - After a bad night's sleep
 => ./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.gmi 2022-08-27 - Gemtexter 1.1.0 - Let's Gemtext again
diff --git a/index.gmi b/index.gmi
index 52574e03..81bf4980 100644
--- a/index.gmi
+++ b/index.gmi
@@ -30,6 +30,7 @@ If you reach this site via the modern web, please read this:
 
 ### Posts
 
+=> ./gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.gmi 2022-11-24 - I tried Doom Emacs, but I switched back to (Neo)Vim
 => ./gemfeed/2022-10-30-installing-dtail-on-openbsd.gmi 2022-10-30 - Installing DTail on OpenBSD
 => ./gemfeed/2022-09-30-after-a-bad-nights-sleep.gmi 2022-09-30 - After a bad night's sleep
 => ./gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.gmi 2022-08-27 - Gemtexter 1.1.0 - Let's Gemtext again