3 ms·
Looks cool, but I doubt I'll use it: switching between modes when using shell isn't very comfy. Actually, every time when I see "vim-mode in <something>" (like
by krick 12y ago
Looks cool, but I doubt I'll use it: switching between modes when using shell isn't very comfy. Actually, every time when I see "vim-mode in <something>" (like shell, IPython Notebook) I wish for the opposite: <something> in vim. But stuff like Emacs or even Atom seems to be more flexible for that purpose, usually all these "<something> in vim" don't really work (or even couldn't be implemented due to inability to show graphics inside the vim (gvim) window). It's a shame.
- hammerandtongs 12y agoFrom my experience with people and their vim knowledge, not "set -o vi" on their shell is what holds them back from becoming truly good at vim. Yes it's uncomfortable but that's most likely a result of a person's disfluency in vim itself. If you are having problems with vi in bash its likely that you aren't using w W b B cw dw D a A regularly in vim either.
- sevensor 12y agoI found that I just couldn't get used to `set -o vi`, despite using vim exclusively for editing. I think my muscle memory for bash was too well-developed by the time I found out about `set -o vi`.
- krick 12y agoI guess I'm pretty damn fluent in vim. But I use emacs-style shortcuts in shell and don't imagine why I would ever switch.
- hammerandtongs 12y agoBecause esc-b esc-b esc-b is much more painful then esc b b b
- blux 12y agoI agree. Neovim brings promises to improve this situation drastically by separating the presentation logic from the editor core functionality, more easily allowing for embedding Vim functionality in 3rd party applications.
- dllthomas 12y agoI find switching modes in the shell quite comfy, for whatever that's worth. I keep getting bit by little incompatibilities, though - lack of support for W, most recently.