I spent some time this weekend creating an init.lua from scratch in order to find the holes in my understanding. This is partly because I was trying to prepare notes to share with friends and partly because I know Neovim can do more than what I was asking of it.
I was pretty sure I knew how to get the Lazy add-on working in order to be able to fetch other add-ons, so I started there. And that went smoothly enough. So then I started pulling in pieces of my previous configuration, very small pieces, so I could see how they worked. I had some trouble getting the language server protocol (LSP) stuff working. I did get it in the end by way of the nvim-lspconfig add-on. Along with Telescope, tree-sitter, a markdown renderer, and marksman.
This necessitated revisiting zen-mode as I don’t like to have all that rendered markdown noise on all the time. I tend to toggle zen mode on while I do my writing, then toggle it off to make sure I didn’t break some table or something. Playing around with the Lua functions for that I got a better understanding of the various key bindings, and cleaned some of those up. I ended up grabbing a bunch of add-ons that I don’t think I’m going to want to keep long term, but they’re nice in the interim. Like something called with-key that starts to show key bindings and their descriptions as you use them. I can see this getting annoying once I don’t need the reference for all of these new things.
Speaking of new things: I’ve been using Edgy to put stuff at the edges of my screen in a consistent location. And I set the options for opening new splits to always be to the right and below. I didn’t expect it to be so comfortable, but it’s working well. I suspect it will be less jarring for those over-the-shoulder witness moments, as it kind of makes it like other editors with tools and explorers to the left and body to the right.
I still need to learn more about LSP and auto completion. While path auto completion is nice in that I can make links to other documents with a preview, or links to sections in other documents like what Obsidian does, I’d really like the ability to complete links based on the titles of documents from their YAML headers. I might also start looking at how dashboards work because it would be nice to see recent notes listed as titles and dates and maybe a little snippet of git history.
created: 2025-01-11
(re)generated: 2025-01-11
text/geminiThis content has been proxied by September (ba2dc).