# .inputrc for Nelson's preferred setup. Configures GNU readline programs.
#   Home, End and the arrows are made to work,
#   Insert is bound to kill-line
#   f13 is bound to delete-char
#   The control keys that did these functions are turned off.
# these bindings are for xterm, vt100, rxvt, and linux console

# Insert means kill-line, f13 (delete key in my X config) means delete-char.
"\e[2~": kill-line
"\e[25~": delete-char

# also, make the linux console delete meen delete-char
"\e[3~": delete-char

# Now for home and end. These are nonstandard keys (no vt100 versions?),
# so there are lots of different versions. Some xterms even send the exact
# same codes for both keys! The escape codes those generate are configurable
# in xterm, but I don't know how.

# I do not think any of these bindings cause conflicts with other keys,
# but if you notice weird behaviour try removing the ones you don't need.
# You can do "cat > /tmp/foo" and hit the home and end keys, then look at
# the file in emacs, to see what sequences those keys are sending.

# First, XFree86 3.1.1 (Slackware 2.1) xterm had these bindings.
"\e[\C-@": beginning-of-line
"\e[\M-\C-p": end-of-line
# Same end keycode with the high bit stripped courtesy of rlogin, sigh.
"\e[\C-p": end-of-line

# XFree86 3.1.2 (Redhat 2.0) xterm has a different end key.
"\e[e":end-of-line

# terminfo versions?! Emacs sees these sometimes, I think
"\eO\C-@": beginning-of-line
"\eO\M-\C-p": end-of-line

# rxvt versions!
"\e[H": beginning-of-line
"\eOw": end-of-line

# finally, Linux console versions.
"\e[1~": beginning-of-line
"\e[4~": end-of-line

# Now we'll make sure the vt100 bindings for arrow keys are there. It's
# not 100% necessary, but it seems to help.
"\e[A": previous-history
"\e[B": next-history
"\e[C": forward-char
"\e[D": backward-char

# Finally, override old keys so we train away from them.
Control-b: 
Control-f:
Control-p:
Control-n:
Control-e:
Control-a:
Control-d:
Control-k: