bug#56592: closed (29.0.50; Moving between nnselect groups sometimes fails to save marks)

[GNU bug Tracking System]

Your message dated Sat, 18 Feb 2023 13:22:41 -0700
with message-id <87bklq3er2.fsf@melete.silentflame.com>
and subject line Re: 29.0.50; Moving between nnselect groups sometimes fails to 
save marks
has caused the debbugs.gnu.org bug report #56592,
regarding 29.0.50; Moving between nnselect groups sometimes fails to save marks
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
56592: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56592
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 29.0.50; Moving between nnselect groups sometimes fails to save marks
>
>
>
>
> Date: 
>
> Fri, 15 Jul 2022 23:43:43 -0700
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)
>
>
>
>
> Hello,
>
> You need a notmuch setup to reproduce this, though maybe other
> gnus-search backends would show it too.  Create two nnselect groups
> where the query for the second includes some of the messages in the
> first group.  This is what I am using:
>
>     first group, nnselect:Weekday, has query
>       "to:spwhitton@spwhitton.name or to:spwhitton@arizona.edu"
>
>     second group, nnselect:Weekend, has query
>       "to:spwhitton@spwhitton.name".
>
> So, messages addressed to spwhitton@spwhitton.name appear in both.
> Ensure there are unread messages addressed to spwhitton@spwhitton.name.
> Enter the first group, mark one of those messages addressed to
> spwhitton@spwhitton.name as read.  Go to the last message, use 'n n' to
> move to the next unread group.
>
> The message that was marked as read reappears, unread, in the second
> group.  If you quit to the group buffer and reenter the first group,
> it's unread again there.
>
> By contrast, if you mark the message as read in the first group and then
> type C-x C-s, and only then do 'n n' on the last message, the marks are
> properly saved and the message does not appear unread in the second
> group.
>
> I have nnselect-rescan t for the groups, in case that is relevant.
>
> -- 
> Sean Whitton
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: 29.0.50; Moving between nnselect groups sometimes fails to save marks
>
>
>
>
> Date: 
>
> Sat, 18 Feb 2023 13:22:41 -0700
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13)
>
>
>
>
> Hello,
>
> On Fri 15 Jul 2022 at 11:43PM -07, Sean Whitton wrote:
>
> > You need a notmuch setup to reproduce this, though maybe other
> > gnus-search backends would show it too.  Create two nnselect groups
> > where the query for the second includes some of the messages in the
> > first group.  This is what I am using:
> >
> >     first group, nnselect:Weekday, has query
> >       "to:spwhitton@spwhitton.name or to:spwhitton@arizona.edu"
> >
> >     second group, nnselect:Weekend, has query
> >       "to:spwhitton@spwhitton.name".
> >
> > So, messages addressed to spwhitton@spwhitton.name appear in both.
> > Ensure there are unread messages addressed to spwhitton@spwhitton.name.
> > Enter the first group, mark one of those messages addressed to
> > spwhitton@spwhitton.name as read.  Go to the last message, use 'n n' to
> > move to the next unread group.
> >
> > The message that was marked as read reappears, unread, in the second
> > group.  If you quit to the group buffer and reenter the first group,
> > it's unread again there.
>
> I have been discussing this with Andrew Cohen and believe, at least for
> now, that it's not a bug: the user is required to set the
> nnselect-regenerate group parameter non-nil in this sort of case.
>
> -- 
> Sean Whitton
>
>
> --- End Message ---