2

I'm switching to vim!

 3 years ago
source link: https://dev.to/siddharthshyniben/i-m-switching-to-vim-867
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client
I'm switching to vim!

I just took a short look at the (neo)vim docs, and I'm officially moving to (neo)vim (and tmux)! I have just used it for a few days, but I really can feel the power it gives me. Not to mention that it really saves my 6GB ram for other uses.

A snapshot of my coding session

And I encourage all of you to do the same. It really is super faster (I come from vscode, and it is really faster). Vim has everything you need – Syntax highlighting, Split screen, File explorers(!), Autocomplete(!), Tabs, Folding lines(!), Indentation autofixing(!), macros, line bookmarks, integrated terminal like interface and what not (I should make an article on it soon). Vim is basically equivalent to VSCode for me.

Discussion (12)

pic

CollapseExpand

It's great that you changed to vim, seems very exciting! It would be cool if you could explain the process on how you changed to vim. Personally I use VSCode with vim extension for keyboard shortcuts. And I think it would be really cool to move fully to vim, but it's hard... first problem is file navigation. VSCode makes it so easy to open up files using ctrl/command + p. There might be some other stuff that I'd miss from VSCode when moving to vim but file navigation is my road blocker I guess.

How did you overcome that?

Comment button Reply

CollapseExpand

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:

Comment button Reply

CollapseExpand

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

Thread

Thread

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

Thread

Thread

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....

Comment button Reply

CollapseExpand

Ok, text editing using vim is my favorite time of the day
But how about debugging? Go to definition?

Comment button Reply

CollapseExpand

for (n)vim is vimspector and vim-dap. vimspector is quite good, but i dont have experience with dap.

For general heavy IDE stuff - take a look in coc-vim this thing supports a lots of stuff like quickfix, go to definition/reference, show docs, and some other codeactions. This extension supports most of the features which a lsp is providing.

But here its maybe worth it to take a look in to the nvim lsp feature which should cover the same stuff.

But vim ist still just only a text editor. The learning curve is high, and most of the time you will at least pay with your time to adapt, and have maybe script addiotional stuff, that it can support your workflow. (like trigger your builds, tests or debug session with a shortkey)

Comment button Reply

CollapseExpand

I actually don't use my IDE for debugging. So I'll never know the difference, I guess?

I actually don't use most of my IDE, so I'm really comfortable with this transition.

Comment button Reply

CollapseExpand

Vim is pretty great. But, the UI is pretty ugly and it's pretty difficult to use (at least for me).

Note: I usually use Atom for small project (since Atom is pretty slow for large project), Visual Studio Code for debugging, and Sublime Text for large project.

Comment button Reply

CollapseExpand

For me, I just don't use the tools it provides too much. But it's not that ugly for me, especially because I have made TUIs and also my font does a great job at ligatures

Comment button Reply

CollapseExpand

If you've changed to vim without any way back, you might say it's SINK OR VIM for you. 😂

Comment button Reply

CollapseExpand

I'm also thinking of switching to Vim after seeing another developer code faster than his shadow! more than assimilating all the shortcuts !! ;)

Comment button Reply


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK