Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus nnmaildir and notmuch
Date: Fri, 24 Mar 2017 11:47:13 -0700	[thread overview]
Message-ID: <8760iyfr66.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lgru7k15.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Erik Colson <eco@ecocode.net> writes:
>
>> Erik Colson <eco@ecocode.net> writes:
>>
>>> So this is more of a enhancement request for nnir.
>>
>> And I should definitely RTFM
>>
>> "The nnir group made in this way is an ephemeral group, and some changes
>> are not permanent: aside from reading, moving, and deleting, you can’t
>> act on the original article. But there is an alternative: you can warp
>> (i.e., jump) to the original group for the article on the current line
>> with A W, aka gnus-warp-to-article. Even better, the function
>> gnus-summary-refer-thread, bound by default in summary buffers to A T,
>> will first warp to the original group before it works its magic and
>> includes all the articles in the thread. From here you can read, move
>> and delete articles, but also copy them, alter article marks,
>> whatever. Go nuts."
>>
>> It kinda makes the notmuch search engine loose its purpose, but at least
>> it is documented :)
>
> No, I think this is supposed to work -- at any rate, there is code in
> nnir for handling this. I'll try to take a look later.

Okay, I looked at it, and the basic problem is that marks from ephemeral
groups are explicitly not propagated.

The practical definition of an ephemeral group is, "does it have a
quit-config parameter", ie, will it be made to disappear somehow when
the user leaves the summary. All `gnus-group-ephemeral-p' does is checks
if a quit-config parameter is present.

`gnus-summary-exit' is responsible for making marks permanent. It checks
for a quit-config parameter, and if it's present prevents a whole lot of
stuff from happening -- including making the marks permanent. I opened
an nnir group and manually killed the quit-config parameter, and can
confirm marks were propagated when I exited the group.

So that's where we are. nnir groups are supposed to be ephemeral, but
that means marks won't be propagated. So long as
`gnus-group-make-nnir-group' uses `gnus-group-read-ephemeral-group', we
can't avoid this, as the latter function unconditionally installs a
quit-config parameter.

Andy, I wonder if any of your local changes affect this behavior?

Thanks,
Eric




  reply	other threads:[~2017-03-24 18:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  9:51 Erik Colson
2017-03-23 15:25 ` Eric Abrahamsen
2017-03-23 15:31   ` Eric Abrahamsen
2017-03-23 15:47     ` Eric Abrahamsen
     [not found] ` <afcec017ee42495d979cc97a6f638276@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
     [not found]   ` <87shm3ex6p.fsf@t3610>
2017-03-23 18:58     ` Eric Abrahamsen
2017-03-24  0:38 ` Andrew Cohen
2017-03-24  1:17   ` Eric Abrahamsen
2017-03-24  8:00   ` Erik Colson
2017-03-24  8:23     ` Erik Colson
2017-03-24  8:29       ` Erik Colson
2017-03-24 15:48         ` Eric Abrahamsen
2017-03-24 18:47           ` Eric Abrahamsen [this message]
2017-03-26  4:51             ` Andrew Cohen
2017-03-26  6:05               ` Andrew Cohen
2017-03-26 16:32               ` Eric Abrahamsen
2017-03-27  1:09                 ` Andrew Cohen
2017-03-27  4:33                   ` Eric Abrahamsen

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=8760iyfr66.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).