Gnus development mailing list
 help / color / mirror / Atom feed
From: Gijs Hillenius <gijs@hillenius.net>
To: ding@gnus.org
Subject: Re: Marks added in nnir search buffers don't propagate to the actual groups?
Date: Thu, 29 Nov 2018 09:35:43 +0100	[thread overview]
Message-ID: <87h8g0ffhc.fsf@hillenius.net> (raw)
In-Reply-To: <87muptvx9c.fsf@ericabrahamsen.net>

On 28 November 2018 11:05 Eric Abrahamsen, wrote:

> 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.

This is also how I understand Gnus. I nearly automatically do A W
gnus-warp-to-article to set or remove tickmarks






  reply	other threads:[~2018-11-29  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 19:05 Eric Abrahamsen
2018-11-29  8:35 ` Gijs Hillenius [this message]
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=87h8g0ffhc.fsf@hillenius.net \
    --to=gijs@hillenius.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).