unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: notmuch@notmuchmail.org
Subject: Re: loss of duplicate messages
Date: Wed, 15 Sep 2010 19:53:41 -0500	[thread overview]
Message-ID: <87iq26mru2.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <878wb7wsnt.fsf@servo.finestructure.net> (Jameson Rollins's message of "Fri, 05 Feb 2010 11:31:34 -0500")

jrollins at finestructure.net (Jameson Rollins) writes:

> I'm not exactly sure what the correct behavior is here, but I would
> actually like to see my messages sent to the list returned to me.
> It's a way of verifying that they did go to the list, as well as
> getting a feeling for the round trip time.  I personally wouldn't mind
> just seeing both copies of the message returned by notmuch, as I can
> just delete one of them if I don't want it to turn up again.  Would
> this behavior be problematic in any way?  Do folks have suggestions of
> other behaviors that might get around this problem?

I'm not sure what the current plan is, but please consider this a
belated agreement.  It doesn't necessarily need to be the default (and
perhaps shouldn't be), but I'd like to have some way to ask notmuch for
*all* matching messages (regardless of message id) -- perhaps via an
--include-duplicates argument to search/show/count, etc.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

  parent reply	other threads:[~2010-09-16  0:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 16:31 loss of duplicate messages Jameson Rollins
2010-02-05 17:25 ` Marten Veldthuis
2010-02-05 17:49   ` Jameson Graef Rollins
2010-02-05 19:39     ` micah anderson
2010-02-05 19:47       ` Jameson Rollins
2010-02-05 21:26         ` micah anderson
2010-02-24 21:10 ` Jameson Rollins
2010-09-16  0:53 ` Rob Browning [this message]
2010-11-12  1:31   ` Carl Worth

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iq26mru2.fsf@raven.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).