Probably the wrong heading, but I wasn't sure where this
fits. In mutt, the backspace key is mapped to 'go back a
line' when reading a message. This works fine in xterm,
nxterm and gnome-terminal. In rxvt and wterm (variant on
rxvt, found at wm.current.nu/files/wterm-6.2.6.tar.gz),
hitting it produces "key not bound". This might be mutt,
of course. (I am using mutt 0.95.5-i, slang-based.) But I
was told that this is more an xterm/rxvt thing. 'printenv'
in rxvt tells me the TERM is 'xterm', but I don't know
other settings I could try to see if this goes away. I
tried using 'delete' instead of backspace, but that didn't
work either. At the command line, they work as I'd expect
(backspace deletes the character behind, delete the one
ahead), but within mutt, no.
is this still happening? I think rxvt, konsole, kvt, xterm, etc. now
all properly are sending ^? for backspace (not ^H). However, mutt may
not understand this keysequence by default, and may need attention.
xterm & gnome-term send ^H. rxvt sends ^?.
fixed for next release.
Commit pushed to master at https://github.com/openshift/openshift-docs
Merge pull request #5063 from bfallonf/dev_guide_links
Issue 4878 Added links to dev_guide/overview