4 ms·

> As a bonus, using a full featured IDE like one of the JetBrains products, but with the Vim plugin, is win win. I refused to use Visual Studio for code editin

> As a bonus, using a full featured IDE like one of the JetBrains products, but with the Vim plugin, is win win. I refused to use Visual Studio for code editing until ViEmu came along. These days I use VsVim. vi is fantastic for editing/writing and using the other niceties of Visual Studio is a win-win, as you said.

transpostmeta 8y ago
This cannot be overstated. 90% of the advantages of VIM is the modal editing interface, which can be used beautifully in Visual Studio, Visual Studio Code, IntelliJ IDEA, and other nice IDEs. The VIM way is a very good way of editing text. IDEs offer a lot more than editing text. Faking an IDE within a text editor with random plugins is terrible. Emulating VIM text editing within a real IDE is amazing. Just use VIM keybindings in your industry standard IDE, you will be able to use all the tips in the linked article and still not miss out on anything offered by the IDE. The only problem is that the VIM keybindings are integrated into direct text editing, but not the IDE UI. For example, in Visual Studio, IntelliSense offers you a choice of possible completions for a variable name you are typing. You can only navigate these choices with your cursor keys, rather than with the VIM-style jkl; keys. But it's a small price to pay for really good text-editing qualities!
- learc83 8y ago
  > You can only navigate these choices with your cursor keys, rather than with the VIM-style jkl; keys. But it's a small price to pay for really good text-editing qualities! I have ctrl-j and ctrl-k mapped to down and up on my keyboard for just this reason. If you have a keyboard that supports macros it's easy to do and it works for all those annoying places in Visual Studio and the rest of the OS you need to use arrow keys for.
sjy 8y ago
There is a loss though, which is that Visual Studio is incredibly slow, and editor latency has "important effects on typist behavior and satisfaction" [1]. You wouldn't want to use Visual Studio to edit a single config file, unless you already had it open for a big programming project. Adding a Vim binding plugin makes things worse and often introduces a startup delay before the editor enters normal mode, meaning your first command gets typed into the file unless you pay attention and wait for the UI to get ready. Vim opens even ridiculously large files that have no place in a text editor instantly, every time. [1]: https://pavelfatin.com/typing-with-pleasure https://pavelfatin.com/typing-with-pleasure

transpostmeta 8y ago

This cannot be overstated. 90% of the advantages of VIM is the modal editing interface, which can be used beautifully in Visual Studio, Visual Studio Code, IntelliJ IDEA, and other nice IDEs. The VIM way is a very good way of editing text. IDEs offer a lot more than editing text. Faking an IDE within a text editor with random plugins is terrible. Emulating VIM text editing within a real IDE is amazing. Just use VIM keybindings in your industry standard IDE, you will be able to use all the tips in the linked article and still not miss out on anything offered by the IDE. The only problem is that the VIM keybindings are integrated into direct text editing, but not the IDE UI. For example, in Visual Studio, IntelliSense offers you a choice of possible completions for a variable name you are typing. You can only navigate these choices with your cursor keys, rather than with the VIM-style jkl; keys. But it's a small price to pay for really good text-editing qualities!

learc83 8y ago
> You can only navigate these choices with your cursor keys, rather than with the VIM-style jkl; keys. But it's a small price to pay for really good text-editing qualities! I have ctrl-j and ctrl-k mapped to down and up on my keyboard for just this reason. If you have a keyboard that supports macros it's easy to do and it works for all those annoying places in Visual Studio and the rest of the OS you need to use arrow keys for.

sjy 8y ago

There is a loss though, which is that Visual Studio is incredibly slow, and editor latency has "important effects on typist behavior and satisfaction" [1]. You wouldn't want to use Visual Studio to edit a single config file, unless you already had it open for a big programming project. Adding a Vim binding plugin makes things worse and often introduces a startup delay before the editor enters normal mode, meaning your first command gets typed into the file unless you pay attention and wait for the UI to get ready. Vim opens even ridiculously large files that have no place in a text editor instantly, every time. [1]: https://pavelfatin.com/typing-with-pleasure https://pavelfatin.com/typing-with-pleasure