GNU bug report logs -
#56592
29.0.50; Moving between nnselect groups sometimes fails to save marks
Previous Next
Reported by: Sean Whitton <spwhitton <at> spwhitton.name>
Date: Sat, 16 Jul 2022 06:44:02 UTC
Severity: normal
Found in version 29.0.50
Done: Sean Whitton <spwhitton <at> spwhitton.name>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sat, 18 Feb 2023 13:22:41 -0700
with message-id <87bklq3er2.fsf <at> 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 <at> gnu.org.)
--
56592: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56592
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
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 <at> spwhitton.name or to:spwhitton <at> arizona.edu"
second group, nnselect:Weekend, has query
"to:spwhitton <at> spwhitton.name".
So, messages addressed to spwhitton <at> spwhitton.name appear in both.
Ensure there are unread messages addressed to spwhitton <at> spwhitton.name.
Enter the first group, mark one of those messages addressed to
spwhitton <at> 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
[Message part 3 (message/rfc822, inline)]
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 <at> spwhitton.name or to:spwhitton <at> arizona.edu"
>
> second group, nnselect:Weekend, has query
> "to:spwhitton <at> spwhitton.name".
>
> So, messages addressed to spwhitton <at> spwhitton.name appear in both.
> Ensure there are unread messages addressed to spwhitton <at> spwhitton.name.
> Enter the first group, mark one of those messages addressed to
> spwhitton <at> 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
This bug report was last modified 2 years and 95 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.