From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218 Description of problem: Even with `all menu mnemonics' disabled in the gnome-terminal Keybindings editor disabled, Alt-backspace doesn't work the same as Alt-Ctrl-H like it did in earlier releases. It used to delete the entire word to the left, like it does in Emacs. Now it only deletes one character. This may be the result of a change in XFree86, since xterm also fails to recognize Alt-backspace now, but it may well be something in gnome-terminal or in gtk+. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Start gnome-terminal 2.Enter a few words into bash 3.Try to delete the last word with Alt-backspace Actual Results: It deletes only one character Expected Results: It should delete the entire word Additional info:
If your X events are right, in "xev" alt backspace will show as state = 0x8, BackSpace. If that shows up right it's probably a terminal issue, otherwise probably X keymap issue.
Here are the events I get for Alt-Backspace: KeyPress event, serial 20, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17005674, (73,88), root:(750,615), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 25, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17006091, (73,88), root:(750,615), state 0x8, keycode 22 (keysym 0xff08, BackSpace), same_screen YES, XLookupString gives 1 bytes: " KeyRelease event, serial 25, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17006158, (73,88), root:(750,615), state 0x8, keycode 22 (keysym 0xff08, BackSpace), same_screen YES, XLookupString gives 1 bytes: " KeyRelease event, serial 25, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17006630, (73,88), root:(750,615), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: "" Looks like it's a terminal issue, then...
This should be fixed in 0.10.9 and later. Please reopen this bug ID if you find that this is not the case.
*** Bug 81475 has been marked as a duplicate of this bug. ***
Confirmed fixed in phoebe2.