Tootfinder

God, what a fucking asshole.
Anyways, I've already spent some time removing #neovim from about half of my build/development containers. For now I'm going back to #vim, but once vim-classic or #evi

I've streamlined the way #Neovim manages my LSP, Linting, and Formatters. Just sharing my approach with you in this #post:
https://

Q: Where is the code? What you've been doing whole day?
A: Figuring out why kewords are red instead gruvbox aqua blue in my #neovim
Q: Oh I see, carry on!
vim.hl.priorities.semantics_tokens = 95
You can take my treesitter syntax highlighting from my cold, dead hands.

I've rebuilt my #neovim config to benefit from version 0.12 and I've learned some new things in the process. Beyond what has been reported everywhere already, here are the small tips I'd like to share with you:
https://

Rework my #Neovim config to finally benefit from the recent major changes. Since I was on it, I've also revisited the entire config, some plugins, replaced some with simple functions... It was a lot of fun. It's been a long time since I had a chance to tweak Neovim that much and it felt good :)

Looks like I got a little ahead of myself. My last post about my new #neovim config left out quite a bit of what I wanted to share. Better late than never, time for an update! ^^
⁨https://www-gem.codeberg.page/vim_2026…

Freedom of speech, unless you don't share my views.
There's a good reason Soviet gulags and prisoner transports were always full.*
*I know it was mostly not about freedom of speech. It was about needing forced labor.
#neovim