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 135080 - gnome-terminal disable all menu access keys does not disable alt-#
gnome-terminal disable all menu access keys does not disable alt-#
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: Keybindings
2.5.x
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
gnome-love
Depends on: 672433
Blocks:
 
 
Reported: 2004-02-21 22:36 UTC by ccheney
Modified: 2016-02-21 14:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Digital (189 bytes, application/pgp-signature)
2004-02-21 22:36 UTC, Unknown User
Details

Description ccheney 2004-02-21 22:36:49 UTC
Distribution: Debian testing/unstable
Package: gnome-terminal
Severity: major
Version:  2.5.x
Synopsis: gnome-terminal disable all menu access keys does not disable alt-#
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.5.x
Description:
Description of Problem:

I don't know if the other key shortcuts aren't disabled but disabling
all menu access keys definitely does not disable alt-# shortcuts. I
wanted to disable the shortcuts so that I can use alt-# in irssi channel
changing.

Steps to reproduce the problem:

1. Edit->Keyboard Shortcuts
2.  Click "Disable all menu access keys"

Actual Results:

It does not disable the alt-# keystroke shortcuts so if I have tabbed
terminals it still switches terminals instead of passing alt-# (eg alt-1
alt-2 alt-3) through to irssi.

Expected Results:

It should disable the alt-# hotkeys for tabbed terminals and pass the
keystrokes through to irssi.

How often does this happen?

Everytime, and has since 2.4, I actually maintain KDE for Debian so was
very busy and forgot to file the bug the last time I tried out gnome.

Additional Information:





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-21 17:36 -------

Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.

Comment 1 Mariano Suárez-Alvarez 2004-02-23 05:03:59 UTC
Note that that checkbox disables the menu access keys (lik alt-F to
get to the File menu), not the keyboard shortcuts (those you can edit
in the /Edit/Keyboard Shortcuts... dialog) All of the latter, in fact,
should be working when the checkbox is checked.

One thing I can think of is that you could set up your keyboard
shortcuts so that Ctrl+Alt+1 goes to the first tab, and so on. I'm
open to alternatives on gnome-terminal's side, though...
Comment 2 ccheney 2004-02-23 05:13:49 UTC
It would be nice if it was possible to completely disable shortcuts 
via a similiar (or even the same) checkbox so that apps that use more 
keys than usual can be used simply by checking that option instead of 
having to remap your keys and then possibly again later for a 
different app.
Comment 3 Mariano Suárez-Alvarez 2004-02-23 05:24:58 UTC
Another checkbox I doubt... 

We could disable both menu accels and kb shortcuts with that checkbox.
-All- of them in one big swoop.

That would probably remove the need for the “Disable menu chortcut
key“ checkbox, too, I guess.
Comment 4 ccheney 2004-02-23 05:31:48 UTC
Yes, that sounds good.
Comment 5 terry 2004-11-11 19:08:50 UTC
I have noticed new behaviour in shift-F10 from version 2.2.2 

it now pops up a context menu, which coincidentally, is a big problem here
for an application
Comment 6 Christian Persch 2008-05-29 19:49:27 UTC
This might be fixed by removing the UI manager's accel group from the window, I think.
Comment 7 Christian Persch 2016-02-21 14:58:04 UTC
This has been possible since a long time, just disable those shortcuts from the Shortcuts tab in the Preferences dialogue.