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 726537 - vte/g-t: easily disable special handling of any key
vte/g-t: easily disable special handling of any key
Status: RESOLVED OBSOLETE
Product: vte
Classification: Core
Component: general
0.35.x
Other Linux
: Normal minor
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-17 14:07 UTC by Egmont Koblinger
Modified: 2021-06-10 14:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Egmont Koblinger 2014-03-17 14:07:12 UTC
For a terminal emulator, many people find it more important that all the keys generate the corresponding escape sequences rather than do stuff with the terminal's chrome. For others (e.g. for accessibility) the other option should remain available.

Currently the way to achieve this is inconsistent and incomplete. Ideally, all such possibilities should be configurable via user-friendly prefs. (To make it more complicated, some keycombos are handled by vte, some others are handled by g-t.) The current situation:

- Alt+mnemonincs, as well as F10 generate escape sequences in vte. G-t hijacks them but offers a config option not to.

- Shift+F10 is hijacked by g-t (emits the escape AND pops up the menu - why both?), a well-known workaround is to unbind it in gtk.css, no UI is offered for this.

- F11 is hijacked by g-t, no possibility to disable this (at least not that I'm aware of).

- Ctrl+F1 used to be hijacked by vte, bug 726438 provides a dirty fix with no way of reverting the original behavior.

- (anything else?)

Also, ChPe points out in bug 726438 comments 6-8:

- He'd rather stop using gtkbinding altogether and just handle all the keys directly in the key press handler. Shift-F10 or Menu key wouldn't work at all then since it's handled by gtkwidget's keybindings. We'd have to handle it ourself then.

- He wonders why bug 153265 used F16, F18, F20 instead of GDK_KEY_(Cut|Copy|Paste).
Comment 1 Egmont Koblinger 2014-03-17 23:43:40 UTC
Relevant nice idea: https://bugzilla.redhat.com/show_bug.cgi?id=1071410
Comment 2 GNOME Infrastructure Team 2021-06-10 14:49:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vte/-/issues/2069.