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 316839 - A better shortcut for next unread
A better shortcut for next unread
Status: RESOLVED DUPLICATE of bug 250873
Product: evolution
Classification: Applications
Component: Mailer
2.2.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-09-21 10:26 UTC by Simone Piccardi
Modified: 2005-09-21 13:21 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Simone Piccardi 2005-09-21 10:26:14 UTC
I do not understand why evolution is using "n" as shortcut for next message.
This task can be much more easily (and naturally) accomplished using the down
arrow. Instad evolution is using the much more complex (and not so much
intuitive) "ctrl-]" as shortcut for next unread. 

I'd like to have a simpler and more natural interface to the next unread
operation, like ad button on the bar, and a simpler shortcut: "n" would be the
natural choice, as also Pan adopted it (using arrows to do next and previuos),
but any single stroke would be better than "ctrl-]". Using the same will be a
bonus also in consistency.

If you have threaded messages next unread is a much more common operation than
simply next, and if you don't have there are no differences. Having already the
up and down arrow to navigate next and previuos email I do not understand the
need to duplicate the behaviour on "n".

I would be useful also to have a behaviour found in thunderbird, that ask if you
want to switch to another folder with unread messages, when there are no more
unread messages in the current folder.
Comment 1 Kjartan Maraas 2005-09-21 10:33:11 UTC
Evo stopped using n and p for next/previous unread. It currently uses , and .
and I think that works ok.
Comment 2 André Klapper 2005-09-21 13:21:07 UTC
kjartan: partially, yeah. see bug 250873, closing as duplicate.
simone: please feel free to add comments to bug 250873.

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