commit a53771573b5df8534a2d4a1b3b7942b650ce5bbe
parent e8b77e13beff3de580e88d02327177382afe4ae1
Author: Eamon Caddigan <eamon.caddigan@gmail.com>
Date: Wed, 11 Dec 2024 20:47:58 -0800
Update the December Adventure log for day 11
Diffstat:
1 file changed, 58 insertions(+), 0 deletions(-)
diff --git a/content/december-adventure/2024-11/index.md b/content/december-adventure/2024-11/index.md
@@ -0,0 +1,58 @@
+---
+title: "2024, Day 11: Another Neovim plugin makes my life easier"
+description: "Instead of code, here’s a list of other useful (neo)vim plugins"
+date: 2024-12-11T19:56:42-08:00
+draft: false
+---
+
+After [my last update]({{< relref "/december-adventure/2024-09/" >}}) I had
+a plan in place to make a short shell script to simplify my usage of
+Neovim’s built-in terminal. But then I found the
+[nvim-unception](https://github.com/samjwill/nvim-unception?tab=readme-ov-file#working-with-git),
+plugin, which does exactly what I want. I set it up and it works great.
+
+So instead of code I’ll take this opportunity to share some of the other
+plugins I use. I only got started installing external plugins after
+I switched from Vim to Neovim about a year ago[^switch]. I’m not running
+_too_ many at the moment, and all of them see near-daily use.
+
+## Some plugins
+
+- <https://github.com/preservim/vim-textobj-quote>
+
+This adds support for the automatic insertion of “curly quotes” in documents
+(cf. \"straight quotes\"). Nice for writing text, but inappropriate for code
+(be sure to enable the built-in `filetype` plugin and enable this only for
+carefully-chosen types of files).
+
+- <https://github.com/preservim/vim-pencil>
+
+This is another plugin to support writing text; it handles both hard and
+soft line wrapping nicely.
+
+- <https://github.com/junegunn/goyo.vim>
+- <https://github.com/junegunn/limelight.vim>
+
+Two more plugins (a matched pair) for writing text. Together they support
+a “focused writing” mode. I use these the least often of the set---they’re
+better for longer documents than short notes---but they’ve helped me get
+into the habit of using Neovim for almost everything I write.
+
+- <https://github.com/jpalardy/vim-slime>
+
+A “code runner”; it automates sending code to a REPL (such as an R or
+IPython session) running in another terminal window or within Neovim’s
+built-in terminal. This replicates what I find to be the most useful feature
+of IDEs (or... _Emacs_).
+
+- <https://github.com/tpope/vim-surround>
+
+This makes it much easier to add or change “surroundings” in text (e.g.,
+quotes, brackets, and tags). This one is funky, and took some getting used
+to, but I couldn’t live without it now. Using it improved my proficiency
+with “text object motions”, makes me feel like a Vim wizard.
+
+[^switch]: I’m inconsistent about how I talk about “Vim” vs. “Neovim”, and
+ in practice I can be pretty haphazard in which one I open. I made the
+ switch to see what all the fuss was about, but since I’m not writing
+ plugins myself, I don’t really experience any differences between them.
