zlacker

[parent] [thread] 2 comments
1. tcoff9+(OP)[view] [source] 2025-01-29 16:00:42
LSP and formatter were really fast to set up. I used kickstart.nvim to get started and lsp and formatter are already mostly configured.

DAP is trickier to set up but is doable. How often are you really debugging though? In the beginning just run both neovim and your ide and just switch when you debug.

Back when LSP wasn’t a thing I still used vim but would just switch to an IDE when I needed to go code exploring and needed to be able to jump to definition and stuff like that. Wasn’t a big deal and was worth it to use both tools because vim is such a superior method for editing text.

replies(1): >>mufasa+oC3
2. mufasa+oC3[view] [source] 2025-01-30 18:20:10
>>tcoff9+(OP)
Thank you for your answer. Some code base have chaotic execution path through a monolithic code base (by design). So, for these code bases, I heavily rely on the debugger. But I like your suggestion to use both of them, I think it's a good way to transition slowly and efficiently.
replies(1): >>tcoff9+X44
◧◩
3. tcoff9+X44[view] [source] [discussion] 2025-01-30 21:19:09
>>mufasa+oC3
Another good way to transition is to use your editor's vim plugin.

Pretty much every IDE has a vim plugin that's at least adequate. I've had good experiences with vscode, jetbrains, and visual studio vim plugins.

[go to top]