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

[Sean Whitton <spwhitton@spwhitton.name>]

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.

Here's a workaround:

    (defun spw/gnus-summary-exit (&rest _ignore)
      (call-process "notmuch" nil nil nil "new" "--no-hooks")
      (with-current-buffer gnus-group-buffer
        (gnus-group-get-new-news t)))
    (advice-add 'gnus-summary-exit :after #'spw/gnus-summary-exit)

-- 
Sean Whitton