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 611799 - Duplicate mnemonic in message list pop up
Duplicate mnemonic in message list pop up
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-03-04 13:13 UTC by darren
Modified: 2012-06-21 10:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32

Attachments
Uses 'g' for meeting instead of the conflicting 'm' mnemonic with 'Move to Folder' (926 bytes, patch)
2012-02-09 10:57 UTC, parthasarathi susarla 		none Details | Review

Description darren 2010-03-04 13:13:09 UTC 
Right-click and 'M' no longer moves an email

Until my latest upgrade (SUSE 11.1->11.2), I could right-click an email's subject line in the list, and press 'M' to activate the context menu for "move to folder". Now it just highlights the entry without selecting it. Pressing again toggles between "move to folder" and "create a meeting".

Presumably the issue is with two items having 'M' as their hotkey. I am using the English (UK) locale on my system.

I'm used to typing the name of the folder to move to, so the new behaviour results in the first letter of the folder name activating an unexpected context menu item. This is confusing and BAD.


Distribution: openSUSE 11.2 (x86_64)
Gnome Release: 2.28.2 (null) (SUSE)
BugBuddy Version: 2.28.0
Comment 1 André Klapper 2010-03-04 23:36:31 UTC 
Any proposal for an unused mnemonic?
Comment 2 parthasarathi susarla 2012-02-09 10:57:42 UTC 
Created attachment 207173 [details] [review]
Uses 'g' for meeting instead of the conflicting 'm' mnemonic with 'Move to Folder'
Comment 3 André Klapper 2012-06-21 10:09:17 UTC 
This was fixed by bug 678397 in 3.5.4.