From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus nnmaildir and notmuch
Date: Thu, 23 Mar 2017 08:31:33 -0700 [thread overview]
Message-ID: <8737e4t3fu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878tnwt3pq.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Erik Colson <eco@ecocode.net> writes:
>
>> Hi,
>>
>> I've setup gnus with nnmaildir as a secondary mail source and using
>> notmuch as indexer/search.
>> Searching with the notmuch nnir backend works very well, and I nicely
>> get a gnus summary buffer of the corresponding results. In that buffer I
>> can select and move messages to other maildir folders and the articles
>> are then effectively moved. I can also mark messages flagged or
>> expirable etc, but when I exit the buffer and relaunch the query, the
>> marks are _not_ saved.
>>
>> How come? Is this expected behavior ? Can it be changed ?
>
> nnir sort of caches its results -- if the group hasn't been killed
> between searches, you'll just see the same results again. nnir doesn't
> support re-scanning, otherwise it seems like it would be reasonable to
> use M-g in an nnir group to refresh the results. I don't know if it's
> possible to implement `nnir-request-scan', or if it simply won't work
> for any ephemeral groups.
>
> To be honest, I just did a little testing, and I couldn't even get marks
> to propagate: I flagged a message (the "real" backend was nnimap),
> exited the group, and the flag wasn't there in the real group, nor in
> the nnir group when I re-ran the search.
Oh, that's because there's no nnimap-request-update-mark deffoo. There
is nnimap-request-set-mark, though -- I don't know why nnir doesn't use
that.
next prev parent reply other threads:[~2017-03-23 15:31 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 [this message]
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
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=8737e4t3fu.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).