Thanks for replying. On Thu, Jun 07, 2007 at 12:14:42PM -0600, Kyle Wheeler wrote: > I suspect this is because you are using the wrong keymap. I'm rather > surprised it works in vim, but I know bash jumps through a lot of ugly > hoops to behave reasonably under such conditions. I don't know how to > fix such a thing permanently (it usually happens for me when I'm > logged into a system remotely), but the temporary fix is to explicitly > define what backspace should be, using the `stty` command. What you > need to do is type in: > > stty erase > > ... with an extra space at the en (after the word 'erase') and then > press control-v and then press the backspace key. That will put up > whatever control-character your backspace key is emitting (it'll > probably look either like this: ^? or like this: ^H ). The command > line will end up looking kinda like this: > > stty erase ^? > > Don't just type in a carot (^) and a question mark (?) though, because > that's not the same thing. Anyway, hit enter, and presto: your > backspace key will work as expected in all programs running in that > particular terminal. > Ok firstly I just noticed that actually the backspace key is working, but it's doing the function of the delete key (i.e. delete the next character).
Weirdly enough, doing ^H in mutt does work as a backspace. Doing `stty erase ^?` (i.e. backspace) doesn't do anything, and if I do `stty erase ^H` then the backspace works in xterm, but doesn't work in vim and still doesn't work in mutt. Confusing, eh? o_O A -- Adam Gray [EMAIL PROTECTED] No Canadian coins.
