After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 436697 - gnome-terminal does not distinguish between Ctrl-Backspace and Backspace
gnome-terminal does not distinguish between Ctrl-Backspace and Backspace
Status: RESOLVED DUPLICATE of bug 420039
Product: vte
Classification: Core
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-07 20:36 UTC by the.dead.shall.rise
Modified: 2008-06-12 22:36 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description the.dead.shall.rise 2007-05-07 20:36:43 UTC
Please describe the problem:
I wanted to bind Ctrl-Backspace to backward-kill-word in zsh, but it seems that gnome-terminal, unlike xterm, generates ^? for both of them(xterm generates ^? for Backspace and ^H for Ctrl-Backspace by default).

Steps to reproduce:
1. Open up Gnome Terminal
2. Press C-v Backspace C-v Ctrl-Backspace
3. Perform the same operation in xterm
4. Feel the difference!


Actual results:


Expected results:


Does this happen every time?
Yep.

Other information:
Tested on Ubuntu Feisty.
Asked around on Ubuntu forums before filing a bug:
http://ubuntuforums.org/showthread.php?t=433674
Comment 1 the.dead.shall.rise 2007-08-30 07:02:27 UTC
Any news on this? It is still very annoying that I can't use Ctrl-Backspace in tilda/gnome-terminal.
Comment 2 the.dead.shall.rise 2007-08-30 07:03:36 UTC
In case it helps, I use zsh.
Comment 3 Christian Persch 2008-05-29 20:58:58 UTC
Have you tried the 'compatibility' tab options in the profile editor (edit->current profile) ?
Comment 4 the.dead.shall.rise 2008-05-29 21:06:17 UTC
Yes, I did, and it didn't work.

gnome-terminal still doesn't distinguish between Ctrl-Backspace and Backspace.
Comment 5 Frederic Peters 2008-06-12 22:36:37 UTC
Note bug 420039 is about the same issue and has a patch attached.

*** This bug has been marked as a duplicate of 420039 ***