Discussion on: I'm switching to vim!

[Siddharth]

The process how I switched to vim? I don't get it. I just installed vim and started using it. No plugins installed yet

About file navigation, there is a builtin file explorer. Just cd to the parent folder, open vim, and run the :Explore command (I guess you know what the :commands)

You get something like this:

[Turutupa]

That actually answered my doubts. So no plugins for file navigation, explorer & buffers as well I suppose. Thanks!

[Siddharth]

You rarely need plugins. Most of the stuff is built in.

[mafflerbach]

But there are plugins for vim as well.
Eg. for filenavigation (with a tree is nerdtree) but netrw (:Explorer) has as well a tree view ( cycling with i between the views)

For fuzzy search over files vim-fzf, i think it handles the open buffers as well, but if not - there is defnitly a plugin for it somewhere....

[Siddharth]

Yeah there are a lot of plugins.

I'm having some trouble installing plugins, especially because I'm using neovim which is a bit different.

[Jonathan Boudreau]

vim-plug should be roughly the same on neovim and vim. Been using it for several years, can recommend.

[Siddharth]

Hmm, but I'm having trouble installing it on my outdated machine

[Jonathan Boudreau]

What is the error you're getting?

[Siddharth]

Fixed it now, used vim-plug instead of vundle

[Jonathan Boudreau]

Nice work, all the best.

[Vinod Nimbalkar]

If you are planning to use neovim version 0.5+ then try github.com/nvim-telescope/telescop..., Its cool.😎

[Siddharth]

I don't think I'll have such deep filesystems... I might try it once i get back to angular

[Turutupa]

wow, that is a cool plugin

[Luke Inglis]

It's an absolute beast. And I mean that in the best way. Pairing that with NeoVim 0.5+'s built in LSP features and you have a lot of VSCode's ground covered.