4 ms·
Using vim as my main editor has incredibly increased my productivity, but learning to use it's macros saved me even a more tremendous amount of time. It takes a
by Seb-C 6y ago
Using vim as my main editor has incredibly increased my productivity, but learning to use it's macros saved me even a more tremendous amount of time. It takes a while to learn to use it, but after that any kind of repetitive task can be done easily with it. And if combined with some bash and vimscript knowledge, it is even greater.
- lars512 6y agoI have to agree wholeheartedly. Learning vim is quite painful, but it keeps paying off for years, even if you choose to use modern editors with vim bindings. The speed of these bindings for navigating and editing code is really unrivalled. I even use the Vimium Chrome plugin, it's a pleasure there too.
- RMPR 6y ago> I even use the Vimium Chrome plugin This plugin can be clumsy sometimes, so I tend to use qutebrowser more often
- silentguy 6y agoI have been using surfingkeys after using vimium for a while. It has way more features (can use it on pdf page tabs too) and you can customize it endlessly with simple javascript. It also has vim binding for editing text in browser. Highly recommended.
- ornornor 6y agoI love vim and have been using it for years. However, I really struggle to find a good config for writing typescript. I see my VSCode colleagues having a blast with auto completion and type signatures lookups. But I could never get this right in vim. Is there a resource about state of the art typescript with vim?
- Seb-C 6y agoTypescript works well using vim-polyglot. For the autocomplete I don't actually use it, but the last time I tried, coc.vim was nice (it is actually the VSCode completion engine in vim).
- ornornor 6y agoI use coc.vim but the autocomplete for types doesn’t work well: if there are several types by the same name you’ll just get a list of the identical names and no way to tell their signature and/or what package they’re from. And if you have a variable or a type, I also can’t get its signature. These are things that VSCode does very well but I don’t want to switch!
- mhotchen 6y agoAfter well over a decade of using vim and trying to use it as an IDE (which I did for a few years full time), I opted to use an actual IDE with a vim plugin instead. I currently use the Jetbrains tools which have an excellent vim plugin developed for them that is only annoying sometimes. It supports macros, and as far as I can tell most of the actual navigation and text manipulation stuff works, even stuff that I didn't find in spacemacs. Even relative line numbers work which has been a godsend. I can navigate tabs using gt/gp, and split windows with :split/:vsplit, but I use the built in file search/navigator for opening files which is far superior to anything I managed to get set up in vim (and I played around a lot). Then I have a simple .vimrc with only a handful of modifications (100 lines or so) and I drop down to real vim for writing small scripts, and any other text composition and refactoring, like comments on HN ;) I hear VSCode has an excellent vim plugin, although having briefly played with VSCode a few months ago I don't think it's the tool for me. I'm happy with something heavyweight for developing projects, and something simpler for quick scripts, slack messages, etc. YMMV of course but this was the route I ultimately ended up taking and I'm happy with my decision.
- martinni 6y agoI highly suggest, [CoC](https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim). It's a simple LSP client, you'll get the exact same coding experience as VSCode. Then you install the [coc-tsserver plugin](https://github.com/neoclide/coc-tsserver https://github.com/neoclide/coc-tsserver) or any LSP server (gopls, omnisharp, etc..) and you're good to go!