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 573279 - Accelerator for "Cancel" and "Close this window" in close dialog is the same
Accelerator for "Cancel" and "Close this window" in close dialog is the same
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
2.25.x
Other All
: Normal minor
: gnome-2-28
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 576020 581184 584071 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-26 14:34 UTC by Ahmad Syukri
Modified: 2009-05-28 11:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
Changes the mnemonics of "Close (Window|Terminal)" to "l" (655 bytes, patch)
2009-03-13 11:24 UTC, Simon van der Linden 		committed Details | Review

Description Ahmad Syukri 2009-02-26 14:34:58 UTC 
The terminal close confirmation dialog has the same accelerator key bound to 'c' for both buttons "Cancel" and "Close this window". Assigning a different key for "Close this window" will make manipulation with keyboard easier.

Other information:
Comment 1 Christian Persch 2009-02-26 15:35:13 UTC 
Will have to wait for 2.27 since we're already in string freeze.
Comment 2 Simon van der Linden 2009-03-13 11:24:52 UTC 
Created attachment 130580 [details] [review]
Changes the mnemonics of "Close (Window|Terminal)" to "l"
Comment 3 Christian Persch 2009-03-13 17:25:26 UTC 
Thanks!
Comment 4 Bruce Cowan 2009-03-19 23:51:49 UTC 
*** Bug 576020 has been marked as a duplicate of this bug. ***
Comment 5 Christian Persch 2009-03-30 17:21:28 UTC 
Fixed in trunk, thanks for the patch!
Comment 6 Christian Persch 2009-05-03 14:20:24 UTC 
*** Bug 581184 has been marked as a duplicate of this bug. ***
Comment 7 Christian Persch 2009-05-28 11:07:36 UTC 
*** Bug 584071 has been marked as a duplicate of this bug. ***