From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: nnir group marks don't propagate?
Date: Fri, 27 Apr 2018 11:25:29 -0700 [thread overview]
Message-ID: <87lgd85wx2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87wowxl0xp.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Andrew Cohen <cohen@bu.edu> writes:
>
>>>>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>> EA> Am I hallucinating this, that marks set in an nnir search group
>> EA> used to propagate to the "actual" server group? I could have
>> EA> sworn this worked, as I think it used to be one of my major uses
>> EA> of nnir searches: to "recover" old messages by ticking them or
>> EA> marking them unread.
>>
>> Yes this should definitely work (and has worked for years and years). It
>> is still working in my setup (just checked) but I am using the
>> gnus-select feature branch.
>>
>> The updating should NOT invoke gnus-summary-update-info; the nnir group info
>> list is not saved to the newsrc (unless you are using permanent search
>> groups). The trick is to update the info for the underlying group that
>> the marked messages are from, and this is done elsewhere. Exactly where,
>> err, I would have to go back and look at nnir.
>
> Good to hear from you!
>
> That's what I thought/hoped. I was sure I'd been using nnir like this
> for years, and it seems to me that it was only in the past month or two
> that it stopped working. Lars has returned from the dead and starting
> fixing bugs, so that was my first suspicion, but it's really hard to
> tell.
I re-built an Emacs from around a year ago, and observed the same
problem, so I guess it's something in my setup, though I can't imagine
what (as usual).
If anyone else happens to see this, do let me know...
E
prev parent reply other threads:[~2018-04-27 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 18:55 Eric Abrahamsen
2018-04-24 1:21 ` Andrew Cohen
2018-04-24 3:48 ` Eric Abrahamsen
2018-04-27 18:25 ` Eric Abrahamsen [this message]
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=87lgd85wx2.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).