Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Marks added in nnir search buffers don't propagate to the actual groups?
Date: Wed, 28 Nov 2018 11:05:03 -0800	[thread overview]
Message-ID: <87muptvx9c.fsf@ericabrahamsen.net> (raw)

Can anyone confirm that changes to marks made in an nnir search buffer
don't propagate to the real articles? Eg you search for an article,
remove its read mark, and then expect to find it unread in the "real"
underlying group. Or you tick it, or whatever.

This is something I noticed ages ago, but sort of figured it was a
problem in my config, but now I've looked into it and so far as I can
tell this is just the way it works.

When I search an nnimap group, and tick an article in the resulting nnir
summary buffer, I can see that nnir asks the nnimap backend about
updating the mark, but the mark is never actually set.
`gnus-summary-exit' is supposed to apply all marks to the backend, but
it very carefully doesn't do that for ephemeral groups (and that code is
ancient).

I sure thought this used to work, though. Maybe nnir used to apply marks
immediately (ie, not waiting for summary exit), but doesn't anymore? Am
I just dreaming? Does anyone have any idea of how this is supposed to
work?

Thanks,
Eric




             reply	other threads:[~2018-11-28 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 19:05 Eric Abrahamsen [this message]
2018-11-29  8:35 ` Gijs Hillenius
2018-11-29  9:36   ` Eric S Fraga
2018-11-29 17:41     ` Eric Abrahamsen
2018-11-29 20:35       ` Eric S Fraga

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

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

  git send-email \
    --in-reply-to=87muptvx9c.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    /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.
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 NNTP newsgroup(s).