I generally prefer vim to vscode. But being able to jump to the file where highlighted functions/classes/etc are defined in vscode is very convenient and something I am not able to do in vim. I'm sure there's probably a vim plugin that can allow me to do this too but I just haven't spent the time to look for it.
Learn Vim (2021)
51–60 of 215 posts
Re: Learn Vim (2021)
#52I generally prefer vim to vscode. But being able to jump to the file where highlighted functions/classes/etc are defined in vscode is very convenient and something I am not able to do in vim. I'm sure there's probably a vim plugin that can allow me to do this too but I just haven't spent the time to look for it.
Re: Learn Vim (2021)
#53Re: Learn Vim (2021)
#54Re: Learn Vim (2021)
#55I generally prefer vim to vscode. But being able to jump to the file where highlighted functions/classes/etc are defined in vscode is very convenient and something I am not able to do in vim. I'm sure there's probably a vim plugin that can allow me to do this too but I just haven't spent the time to look for it.
Re: Learn Vim (2021)
#56I've re-built my neovim config like 3 times this year as I have played with several 'distributions' and styles. SpaceVim, LunarVim, AstroVim, and NVChad to name a few. This last weekend I gave LazyVim a try and it is by far the most sane config setup I have used and I will now be sticking with it. There is a starter repo where you clone it, delete the .git directory and start customizing. https://github.com/LazyVim/L…
https://github.com/helix-editor/helix is the answer mate
I can customize Neovim the way I want and the plugin ecosystem is huge. Maybe when Helix gets there it will be worth the switch.
p.s. kakoune style of modal editing makes so much sense and I wish vim had started out like that.
Re: Learn Vim (2021)
#57Earlier quoted context omitted.
I'm happy to dump NeoVim if Helix is actually better. But is the ecosystem _really_ there yet?
Unfortunately there is no ecosystem. Helix does not provide an extension interface.
Re: Learn Vim (2021)
#58A new user coming to the Vim ecosystem in 2023 would be best served by using Neovim with Lua.
Re: Learn Vim (2021)
#59I generally prefer vim to vscode. But being able to jump to the file where highlighted functions/classes/etc are defined in vscode is very convenient and something I am not able to do in vim. I'm sure there's probably a vim plugin that can allow me to do this too but I just haven't spent the time to look for it.