Tootfinder

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://

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…

🔧 Ships as a language server (harper-ls), a JavaScript library, a Rust crate, browser extensions and editor plugins: VS Code, Neovim, Zed, Obsidian, WordPress block editor, Chrome, Firefox and a macOS desktop app that works in every text field system-wide.

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 :)

Things I've learned today:
- Valgrind does not support AVX512 instructions. That was an adventure because I was writing purposefully bad code at the time...
- However, changed strategies and used `clang` with the `fsanitize=address,undefined` option which seems to work perfectly fine.
#clang

OH: "I dreamt of NeoVim last night."
...
"I dreamt of Deutsche Bahn last night."

“Co-Authored-By: Copilot”
I was ignoring Microsoft and their "free" editor before it was cool. It is just funny how many people felt the need to tell me how greybeard, backward and uncool I am when using #neovim

Free your mind of code formatting and focus on code writing in Neovim thanks to conform.nvim
#blog

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

Have you heard of MRU.nvim before today? I didn't and that's another plugin I was missing to build my perfect Neovim.
#blog