I love Vim, it's just a shame it takes 200 years to setup properly.
but you'll recover that time by not touching your mouse... ;o)
Learn Vim (2021)
41–50 of 215 posts
Re: Learn Vim (2021)
#42For those wanting to practice this, also consider pairing this with Ilya Grigorik's VimGolf >> https://www.vimgolf.com/.
Re: Learn Vim (2021)
#43I've found learning vim--either as a plugin for IntelliJ or Chrome or Firefox or as a minor mode in Emacs or by itself--probably the most productive thing I've done on a computer. I spend all my time editing code. It's incredibly useful to learn how to do that quickly. I went through trying to customise it perfectly but I found it is better--more portable for one thing--to learn its defaults. I enable a couple of thi…
I don’t know about it being unparalleled, but when I am in a terminal I don’t think twice before typing ‘vi’.
And for those who don't know, on most modern Linux-based distributions `vi` is an alias for `vim` which is Vim (Vi IMproved).
Re: Learn Vim (2021)
#44Earlier quoted context omitted.
https://github.com/helix-editor/helix is the answer mate
I'm happy to dump NeoVim if Helix is actually better. But is the ecosystem _really_ there yet?
As with most engineering tools, I think using the word "better" is not necessarily correct. It's a matter of tradeoffs.
For me, I was fed up maintaining code to run my neovim setup the way I want, so I was looking for a configuration distribution or... something else.
Helix was the dead simplicity I was looking for. It has its own warts and drawbacks, but the tradeoffs are well worth it in my experience. I absolutely love Helix!
But if you want your editor to work exactly the way you want and having maximum flexibility is more important, you will not like Helix, which is extremely opinionated and has 95% of what you want in a modern text editor. The other 5% may be a deal breaker for you.
And that's fine! Use the tools you love!
Re: Learn Vim (2021)
#45Earlier quoted context omitted.
I'd honestly point folks towards Helix[0] these days if they don't already have something keeping them on neovim/vim. There's very little in the ways of needing to configure Helix; it has built-in most functionality that you'd find with batteries-included vim "distributions" and it works out of the box with the installed LSP servers on your system. [0]: https://github.com/helix-editor/helix
I've been using helix the last week or so. I can confirm everything "just works". My config file is not a turing-complete nightmare, it's literally 10 lines and took about 15 minutes to set up, most of that being personal preference on UI. Great program. I've tried vim-as-IDE many times and personally I've found that I just don't have the patience/discipline to get it all set up and not have it become a huge time sin…
I had the exact opposite experience just then.
Installed helix, and nothing 'worked'. LSP wouldn't start, syntax highlighting didn't work, and once I did get them working, editing JSX caused strange issues where the autopair functionality created a duplicate of my code several lines above where I was working..
Not particularly impressed tbh.
It was very fast to start and use the fuzzy search though.
Re: Learn Vim (2021)
#46Earlier quoted context omitted.
I don’t know about it being unparalleled, but when I am in a terminal I don’t think twice before typing ‘vi’.
And for those who don't know, on most modern Linux-based distributions `vi` is an alias for `vim` which is Vim (Vi IMproved).
True scotsmen exclusively use ed.
Re: Learn Vim (2021)
#47Earlier 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.
Huge downside for me.
Not that I want to muck around with plugins all day, but having the ability to add a few helper plugins to ease certain tasks is a godsend in terminal editors.
Especially if you really dislike certain defaults packaged with the editor.
Re: Learn Vim (2021)
#48I try to use it in my IDE but there are too many conflicts (>1) and I give up and turn the mode off.
Re: Learn Vim (2021)
#49I 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)
#50I 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.
Neovim + lsp (coc.nvim/ale can do this in vim as well)