4 ms·
"7. Use vi-mode in Your Shell" Tried this and gave it up. Your shell may be (somewhat) vi compatible but the applications you use mostly are not so you'll have
by mtts 14y ago
"7. Use vi-mode in Your Shell"
Tried this and gave it up. Your shell may be (somewhat) vi compatible but the applications you use mostly are not so you'll have to break out of the vi mindset at all sorts of inopportune moments. That, and modal editing, while perfectly alright for text editing, maps rather lousily to command line operations. You're much better off getting used to some basic Emacs-style key bindings that work consistently across a wide number of applications (including OS X text fields, IIRC).
- kittxkat 14y agoWhat I did, for example, was that I enabled vi-mode in my shell but also re-enabled some emacs-keybindings like CTRL-E and CTRL-A for ending and beginning of a command because I learned them like a lifetime ago when I first got used to the shell without even knowing they were emacs-keybindings. But that way I am also able to hit ESC and do a / for a search, like within vim, which I am much more used to than a search in emacs. I found that way combines the best of both worlds.
- jlgreco 14y agoI use vi-mode in my shell but the end/beginning Vi commands (A,I,0,$,etc) are the only ones I find myself using regularly. I also use c[motion] and d[motion] on occasion, but that is pretty much it. I'm not convinced that powerful editing is necessary for the command line, but familiar shortcuts for beginning/end seem very useful.
- dllthomas 14y agoThere are absolutely times that powerful editing is mandatory at the command line; I am skeptical that there are times when powerful editing at the command line is necessary but pulling the line into your $EDITOR (v in vi-mode, ctrl-x ctrl-e in emacs-mode) is not the best way to deal with it.