A spelling rabbit hole
2025-06-18 13:42:06 +01:00 by Mark Smith
I just discovered how to enable spellcheck in neovim. That last word just got a sguiggle under it. Oh my gosh, there are sguigles everywhere now. Ok it‘s squiggle. Few.
I was getting tired of having to spend ages and ages after publishing a post, reading and correcting. Figured there must be a way. But searching around, enabling spellcheck seemed rather tedious.
So I tried to find a configuration for vim that would make it automatic for markdown files, but then discovered, or to be more precise, re-discovered that I am using nvchad so I no longer even have a vimrc file. Oh noes!
After more searching, found that in nvchad you can enable a grammarly LSP, which is a language server, and neovim is an LSP client, i.e. it can connect to any language server, that‘s how it does syntax highlighting btw. Yeah I had to search and read about all that too. Everything is a voyage of discovery these days.
At some point I discovered that with nvchad you can just do a :set spell and spellcheck is turned on. I guess it‘s somehow preconfigured with US english? Anyway turning it off is :set nospell. I learnt some of the spellcheck commands, which are pretty gnarly imho. Now I‘m thinking that this isn‘t an nvchad thing, maybe using :set lasts across restarts? I dunno.
Since I got spellcheck working, I thought, wouldn‘t it be great to have grammarly, because sometimes my grammar isn‘t all that wonderful. And I was installing the lsp via npm and read in some configuration / Readme somewhere that the lsp sends everything you write to the grammarly servers. Duh! Of course it does. That doesn‘t sound good.
IMO, we should really have spellcheck and grammarly functionality baked into the OS.
Anyway just another tech configuration rabbit hole. With any luck, the spelling in my posts might improve a bit going forward. #