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 246546 - Keyboard short cut code Ctrl-I is used twice.
Keyboard short cut code Ctrl-I is used twice.
Status: RESOLVED DUPLICATE of bug 241331
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Anna Marie Dirks
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-07-18 00:11 UTC by jj
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jj 2003-07-18 00:11:41 UTC
Package: Evolution
Priority: Major
Version: 1.4.3
Synopsis: Keyboard short cut code Ctrl-I is used twice.
Bugzilla-Product: Evolution
Bugzilla-Component: Shell

Description:
Description of Problem:

Keyboard short cut code Ctrl-I is used twice. Once for "Edit|Invert
Selection" and again for "File|Import..."

Steps to reproduce the problem:
1. Highlight your favourite mail folder (with lots of unread mail you'll
never have time to read)
2. Decide to mark all the mail unread in the quickest way you can think
of...
3. Press the sequence Ctrl+A , Ctrl+K , Ctrl+I

Actual Results:

The "Evolution Import Assistant" pops up. You have to cancel it and then
click on a single e-mail to invert your selection.

Expected Results:

Expected all e-mails to be un-highligted (ie. Invert Selection to work).
This is the expected behaviour because older versions of Evolution
always did this, and old habits die hard.

How often does this happen?

Always.

Additional Information:

Of course, invert selection I'm sure has other uses beyond this, and it
might be nice to have a quicker way to mark all e-mails read in a folder
anyway.



Unknown reporter: jj@positive-internet.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2003-07-25 20:54:41 UTC

*** This bug has been marked as a duplicate of 241331 ***