[Users] Goto next/prev unread stopped working.

[Dustin Miller]

On Fri, 26 Nov 2021 17:58:14 +0100
"Erik P. Olsen" <epodata at gmail.com> wrote:

> On 2021-11-26 at 16:15:38 Dustin Miller wrote:
> 
> > On Fri, 26 Nov 2021 10:14:05 +0100
> > "Erik P. Olsen" <epodata at gmail.com> wrote:
> >   
> > > Surprisingly the function goto next/prev has stopped working
> > > somehow. It only works on a series of unread mail. Outside of
> > > unread mails it's just a noop. 
> > >     
> > DM: You might need to clarify and/or provide more information for
> > someone to try to help with this:
> > * 1. Your subject and first paragraph seem to me to be saying
> > different things in regard to what mails are affected.  
> 
> OK, I've phrased it incorrectly, here goes: the goto next/prev works
> properly within a folder but it does not goto unread mail in other
> folders. I hope this is clear.
> 
DM: Okay, that's clearer. Interesting. I knew that was possible, but
only because it happened when message-scrolling with the space bar and
I didn't want it to happen. :) I can't give you a definitive solution
on this, but here are a few comments/questions that might help you
and/or others figure it out:

* 1. [I was going to mention the need to know your OS and Claws
  version, but I see you have it in your signature. :) ]

* 2. Any Claws updates (upgrades, downgrades, etc.) that could be
  causing this?

* 3. Any OS updates that could be causing this? (Sometimes a change in a
  third party package that Claws depends on can cause issues.)

* 4. Any intentional / unintentional changes to Claws settings... ?

* 5. If you list a detailed 'Steps to Reproduce' the issue, others can
  see if they can confirm it. (I'm pretty sure there are others on this
  list using Claws on Fedora.) If they can, then it might be a Claws
  bug. If not, then it might be something specific to your system that
  is causing this. If you have another system that you could run Claws
  on, you could also do a similar test yourself.

* 6. Any other information you can think of that might be relevant?
> 
> > * 2. It may also be relevant as to how you are initiating this
> >   function; are you using a toolbar button, going through the menu,
> > or a hot key? If you are using a hot key, there's a chance that
> > this got mistakenly changed somehow. If you look at the menu items
> > you can see what hot keys are assigned, if any; I believe the
> > defaults are 'P' and 'N' for all emails and 'Shift + P' and 'Shift
> > + N' for unread emails.  
> 
> I am actually using both the toolbar buttons and the hotkeys and they
> perform the same way.
> 
> > * 3. Starting Claws with debugging enabled and then checking the
> >   terminal for relevant output may also be helpful, depending what
> > the issue is.  
> 
> Unfortunately, I don't know how to decipher the debug log :-(
> 
DM: I understand. However, it could give you output that you could copy
and paste for someone else to look at that might be able to decipher
it. Not sure you'll need it, but if you look on the Claws website,
you'll also find even more detailed and technical ways of debugging
Claws. Hoping you'll eventually be able to figure this out. ---Dustin
> 
> -- 
> Erik P. Olsen - Copenhagen, Denmark
> Fedora 35/64 bit xfce Claws-Mail 4.0.0 POP3 Gramps 5.1.3 Bacula 11.0.5