Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <info-gnus-english@gnu.org>
Subject: Re: gnus nnmaildir and notmuch
Date: Thu, 23 Mar 2017 17:10:22 +0000	[thread overview]
Message-ID: <87shm3ex6p.fsf@t3610> (raw)
In-Reply-To: <afcec017ee42495d979cc97a6f638276@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Eric Abrahamsen's message of "Thu, 23 Mar 2017 15:25:37 +0000")


[-- Attachment #1.1: Type: text/plain, Size: 507 bytes --]

On Thursday, 23 Mar 2017 at 15:25, Eric Abrahamsen wrote:

[...]

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

I tend to warp to the article in the original group (A W) which then
allows one to do whatever you want with it.  Not ideal, mind you.

-- 
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]



       reply	other threads:[~2017-03-23 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87poh8nwxj.fsf@ecocode.net>
     [not found] ` <afcec017ee42495d979cc97a6f638276@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-23 17:10   ` Eric S Fraga [this message]
     [not found] ` <87shm3zeyf.fsf@hanan.ust.hk>
     [not found]   ` <871stnrtn8.fsf@ecocode.net>
     [not found]     ` <87mvcbqe18.fsf@ecocode.net>
     [not found]       ` <87bmsrqdrl.fsf@ecocode.net>
     [not found]         ` <87lgru7k15.fsf@ericabrahamsen.net>
     [not found]           ` <8760iyfr66.fsf@ericabrahamsen.net>
     [not found]             ` <181fbe86ac6648a4abbea9d352a35e4f@AM4PR01MB1891.eurprd01.prod.exchangelabs.com>
2017-03-26 12:18               ` 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=87shm3ex6p.fsf@t3610 \
    --to=e.fraga@ucl.ac.uk \
    --cc=info-gnus-english@gnu.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).