From: Erik Colson <eco@ecocode.net>
To: Andrew Cohen <cohen@bu.edu>
Cc: ding@gnus.org
Subject: Re: gnus nnmaildir and notmuch
Date: Fri, 24 Mar 2017 09:00:43 +0100 [thread overview]
Message-ID: <871stnrtn8.fsf@ecocode.net> (raw)
In-Reply-To: <87shm3zeyf.fsf@hanan.ust.hk> (Andrew Cohen's message of "Fri, 24 Mar 2017 08:38:32 +0800")
Andrew Cohen <cohen@bu.edu> writes:
> I'm responsible for the code but haven't had time to work on gnus for
> several years. Updating of marks is supposed to work---indeed, it works
> fine for me with imap. I haven't used notmuch but the marks code
> shouldn't depend on that.
Hi Andrew,
I think nnir flag support does work with nnimap when using imap as
search engine. In my particular case I'm using nnmaildir with notmuch
search engine. I'll try with nnimap and notmuch search engine, but that
configuration will break my other imap account so I have to be really
careful setting this up.
At this point, I guess the problem is probably not related to
notmuch. More precisely I think the cause is the nnmaildir backend. Does
this make sense ?
best
--
erik colson
next prev parent reply other threads:[~2017-03-24 8:00 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 [this message]
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=871stnrtn8.fsf@ecocode.net \
--to=eco@ecocode.net \
--cc=cohen@bu.edu \
--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).