Nice work! One small piece of feedback. Maybe I'm alone in this but I'd to see default keybinds and config for LSP. I like to keep my config small and defaultly and this:
You're not alone. I find it crazy that you're supposed to write a callback handler, and then register the handler inside a for loop over each server. This feels more like programming inside a framework, than writing a config file.
For complex things, it's nice to be able to do this. But the benefit of having a built-in client is that it works out of the box. This looks like it requires more configuration than many of the existing (n)vim lsp clients, even for the most basic thing: setting up the keybindings.
I had visions of writing tests and then the AI would do the production code. I think that would be a lot better. Comments are too hard to get right. Good Luck!
- Clean Architecture
- Design Patterns: Elements of Reusable Object-Oriented Software
- Domain-Driven Design: Tackling Complexity in the Heart of Software
- Clean Agile
and forget the rest. Life is short and those books are more than enough.
I've been a using vim for well over a decade. I switched over to neovim for the native LSP support. I spend most of my time programming in neovim but I also have goland installed which I use for high level refactorings such as "extract method" or "change signature". Once I can do these high level refactors with nvim+gopls then I can finally leave goland.
Can't say I really care about more syntax highlighting or lua. Less config is better.
https://github.com/neovim/nvim-lspconfig#keybindings-and-com...
dwarfs my .vimrc