Re: [Evolution] has the "go to next unread message" function changed?

[Bram Mertens <bram-mertens linux be>]

On Sat, 2005-01-08 at 13:53 -0800, Brian Mury wrote: 
> On Sat, 2005-08-01 at 15:47 +0100, Bram Mertens wrote:
> > Before upgrading from evo 1.4.6 to 2.0.3 I could:
> > A: press shift+. to go to the next unread message,
> > B: press ctrl+h to select a thread,
> > C: press ctrl+k to mark it as read and finally
> > D: press shift+. to go to next unread message.
> >
> > Now in evo 2.0.3 A through C work fine [1] but D doesn't work any more.
>
> A and D are the same thing. How can A work and not D?

A and D differ in the fact that with D a thread is selected in stead of
a single message or even, as Guenther tested, multiple messages.

> They all work for me.
>
> > Whenever a thread is selected "go to next unread message" appears to be
> > ignored. Neither the keyboard shortcut nor the menu-option work.
>
> Same here.
>
> > This is on debian testing with fluxbox as WM.
>
>  Fedora Core 3 with Gnome/Metacity.

I am experiencing some issues with focus at the moment but I don't think
the WM has anything to do with this because I get the same behaviour
when I'm running Gnome/Metacity. Are you running version 2.0.3 as well?

--  Mertens Bram "M8ram"   <bram-mertens linux be>   Linux User #349737 #
# debian testing            kernel 2.6.8-1-686     i686     512MB RAM #
# 10:02:22 up 3 days, 21:05,  8 users,  load average: 0.36, 0.23, 0.16 #