Vim Anti-Patterns That Cause Beginners To:Quit

Re:Vim Anti-Patterns That Cause Beginners To:Quit by markenqualitaet on Friday October 08, 2021 @10:36AM (#28799780)

Does (neo)vim offer a similar debugging experience? Visually stepping through code and setting break points and stuff?

I like vim's code navigation, but I miss the autocompletion features of bigger editors. Can you make vim tab complete like sublime? Last I tried, it was never as "one key to rule them all", but required some additional finger-fu and attention. Also moving selected code around (so I can make engine noises) is a must.

Something about VS Code just feels wrong, but it's pretty much exactly enough of an "IDE" for me. Tho, I strongly dislike the project based file management. Would like to have a solid vim setup instead.

[ Parent | on HN ]

Re:Vim Anti-Patterns That Cause Beginners To:Quit by throwawake on Friday October 08, 2021 @11:44AM (#28800517)

Debugging is one of the reasons I keep using vscode. There is vimspector but I never tried that.

For code-completions coc.nvim offers similar config and plugins as vscode. There is official lsp support for neovim now but coc.nvim works fine.

[ Parent | on HN ]

Re:Vim Anti-Patterns That Cause Beginners To:Quit by markenqualitaet on Sunday October 10, 2021 @07:05AM (#28817461)

Thanks.

[ Parent | on HN ]