Turn on emacs line editing mode by default, as this is what most shells do

these days, and the average user expects ^A and arrow keys to work, however
if they know nothing of editing modes, they will think sh(1) just sucks.  It
is likely that because of defaults on most systems and with most shells that
anyone who actually wants vi(1) editing mode will have 'set -o vi'.  This
won't affect existing accounts, this way, of course.  Only accounts with
.shrc from new etc/skel will be affected.  This is much better than making
the change in sh(1).

1 files changed, 7 insertions, 3 deletions

diff --git a/share/skel/dot.shrc b/share/skel/dot.shrc
index fbc2feec7e70..73491698e8e7 100644
--- a/share/skel/dot.shrc
+++ b/share/skel/dot.shrc
@@ -13,9 +13,13 @@
 #
 # umask	022
 
-# Uncomment next line to enable the builtin emacs(1) command line editor
-# in sh(1), e.g. C-a -> beginning-of-line.
-# set -o emacs
+# Enable the builtin emacs(1) command line editor in sh(1),
+# e.g. C-a -> beginning-of-line.
+set -o emacs
+
+# Uncomment this and comment the above to enable the builtin vi(1) command
+# line editor in sh(1), e.g. ESC to go into visual mode.
+# set -o vi
 
 
 # some useful aliases