Neovim

2217 readers

3 users here now

founded 2 years ago

MODERATORS

erlingur@programming.dev

howarddo@programming.dev

kahnclusions@programming.dev

lung@lemmy.world

switching from VSC to VIM (lemmy.ml)

submitted 2 years ago by madeindjs@lemmy.ml to c/neovim@programming.dev

17 comments fedilink hide all child comments

I'm thinking of switching from VSC to VIM because VSC is too heavy in term of ressources usage.

Currently, I use the VSC + VIM extension and I'm pretty happy.

But nowadays, I avoid to open some monorepo projects because it takes too much time and I use the Github explorer instead. Also, I use the mouse too much.

So I finally took the decision to give a try to Neovim.

I initially started with SpaceVIM and it was a good experience. But there is too much magic for me. Also, I have the feeling to not learn VIM.

So I setup CoC with VIM-plug + NerdTree. It looks promising.

Do you have any tips for me?

you are viewing a single comment's thread
view the rest of the comments

[–] zlatko@programming.dev 2 points 2 years ago

I agree, there are several good starting points. But I think it's more important what the OP said about his understanding of it. I think this is a lot more important - WHY do you use plugins, HOW they help you, WHAT can they do. Like, autoimport like vscode does? Autohighlight problems? Check. Check. Autofix linting issues? Check. Find files? Check. Search the project? Check. There's a lot of things that can make your experience way better. Look up some videos. E.g. this one (if you can ignore some twitch memes, I found them mostly fun or tolerable).

Also, when you give up on vim, come back again. It's something that can take many iterations to really "get". Even if things don't work out, try again in a few years.

Also, as an alternative to VSCode, try some native editor. I personally used sublime - for weak machines, it's way better on resources then VSCode and it's electron baggage.