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 678275 - could not setup a shortcut prefixed with 'shift'
could not setup a shortcut prefixed with 'shift'
Status: RESOLVED OBSOLETE
Product: anjuta
Classification: Applications
Component: core application
3.4.x
Other Linux
: Normal minor
: ---
Assigned To: Naba Kumar
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-17 21:53 UTC by Massimo Cora'
Modified: 2020-11-06 20:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Massimo Cora' 2012-06-17 21:53:55 UTC
steps to reproduce:
1. go to edit->preferences->general->shortcuts.
2. explode a fold
3. double click on a shortcut value to enter a new one
4. press the shift key + another one: the shift isn't taken into consideration.

I'd really like to have a shift option as, for instance, compiling should go shift+f7 for the whole project, and f7 for just the current module.
Comment 1 Sébastien Granjoux 2012-06-18 20:51:59 UTC
(In reply to comment #0)
> steps to reproduce:
> 1. go to edit->preferences->general->shortcuts.
> 2. explode a fold
> 3. double click on a shortcut value to enter a new one
> 4. press the shift key + another one: the shift isn't taken into consideration.
> 
> I'd really like to have a shift option as, for instance, compiling should go
> shift+f7 for the whole project, and f7 for just the current module.

It seems that shift+F7 is not accepted by Gtk anymore, Shift+F7 and F7 run the same function. We probably have to change our default shortcuts
Comment 2 André Klapper 2020-11-06 20:22:54 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/anjuta/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.