Re:Writing an editor in less than 1000 lines of code, just f...
by dorfsmay on Sunday July 10, 2016 @03:31PM
(#12066888)
I know k is up, because I constantly <ESC> k in bash, bit the point of using hjkl is exactly not to know which one is what. You set your finger on the keyboard in home position, now your muscle memory does the rest.
[ Parent
| on HN ]
Re:Writing an editor in less than 1000 lines of code, just f...
by coldtea on Sunday July 10, 2016 @04:31PM
(#12067140)
>I know k is up, because I constantly <ESC> k in bash
What is ESC-k supposed to do in Bash?
Re:Writing an editor in less than 1000 lines of code, just f...
by tbirdz on Sunday July 10, 2016 @05:10PM
(#12067287)
The poster probably changed his bash to use vi editing mode with set -o vi. In this mode, <ESC>k would put the text of the last command entered back on the prompt.
Re:Writing an editor in less than 1000 lines of code, just f...
by dorfsmay on Sunday July 10, 2016 @08:23PM
(#12067985)
I do switch deadline to vi mode, since that's the editor I use the most.
I'm always surprised by people who are on the vi/vim side of vi/emacs debates but then use the defaults emacs mode in deadline!