unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: 56592@debbugs.gnu.org
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: bug#56592: 29.0.50; Moving between nnselect groups sometimes fails to save marks
Date: Fri, 15 Jul 2022 23:43:43 -0700	[thread overview]
Message-ID: <8735f17e1s.fsf@athena.silentflame.com> (raw)

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





             reply	other threads:[~2022-07-16  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16  6:43 Sean Whitton [this message]
2022-07-16 13:54 ` bug#56592: 29.0.50; Moving between nnselect groups sometimes fails to save marks Sean Whitton
2022-07-16 14:42 ` Sean Whitton
2022-07-18 20:52   ` Sean Whitton
2022-08-08  0:04     ` Sean Whitton
2023-02-18 20:22 ` Sean Whitton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735f17e1s.fsf@athena.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=56592@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).