News for hackers. Stuff that matters.
Re:Moving efficiently in the CLI by ggm on Friday January 26, 2018 @04:53PM (#16243187)
Its a historical artifact of how in-line edit emerged as a thing for most people. MIT had huge influence in the development of window systems (X10/X11) and adopted emacs string edit mode in most type in boxes. Bash came from a community which had a strong emacs usage. So, the default in both the window system and in the bash shell, was emacs, even if you use ed/ex/vi

Because most people used awk/grep/sed/ed/ex/vi the regex format tended that way. But enough people used tcsh or bash in emacs by default, that shell and omnibox (when browsers eventuated) edit defaulted to emacs.

Thats my theory: accidental happenstance and defaults.

Re:Moving efficiently in the CLI by SmirkingRevenge on Friday January 26, 2018 @06:06PM (#16243610)
And if I'm not mistaken, during that time, the ctrl key was typically where caps lock is today (maybe just on certain machines?) - and that is what influenced the frequent use of ctrl for key shortcuts in libraries lile readline.
Re:Moving efficiently in the CLI by hoosieree on Friday January 26, 2018 @08:41PM (#16244337)
Re:Moving efficiently in the CLI by ggm on Friday January 26, 2018 @08:18PM (#16244264)
may well be. not that escape is so far away from a pinkie, for the modal people (like me)
Re:Moving efficiently in the CLI by SmirkingRevenge on Friday January 26, 2018 @09:33PM (#16244520)
It pretty far away, compared to capslock. Especially on modern laptops.. lile touch bar macs that actually remove the the entirely
Re:Moving efficiently in the CLI by ggm on Saturday January 27, 2018 @06:25AM (#16245799)
Hateful. Annoying. Thank goodness for kbd remapping