Bug 80252 - Alt-backspace is passed to the application as plain backspace
Summary: Alt-backspace is passed to the application as plain backspace
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: vte
Version: phoebe
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
: 81475 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-12-23 10:08 UTC by Alexandre Oliva
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-01-14 04:04:04 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Alexandre Oliva 2002-12-23 10:08:49 UTC 
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:
Comment 1 Havoc Pennington 2002-12-23 16:09:20 UTC 
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.
Comment 2 Alexandre Oliva 2002-12-23 16:59:55 UTC 
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...
Comment 3 Nalin Dahyabhai 2003-01-14 04:04:04 UTC 
This should be fixed in 0.10.9 and later.  Please reopen this bug ID if you find
that this is not the case.
Comment 4 Nalin Dahyabhai 2003-01-14 04:06:04 UTC 
*** Bug 81475 has been marked as a duplicate of this bug. ***
Comment 5 Alexandre Oliva 2003-01-23 14:56:47 UTC 
Confirmed fixed in phoebe2.
Note You need to log in before you can comment on or make changes to this bug.