From: Rob Browning <rlb@defaultvalue.org>
To: notmuch@notmuchmail.org
Subject: Re: [notmuch] loss of duplicate messages
References: <878wb7wsnt.fsf@servo.finestructure.net>
Date: Wed, 15 Sep 2010 19:53:41 -0500
In-Reply-To: <878wb7wsnt.fsf@servo.finestructure.net> (Jameson Rollins's
	message of "Fri, 05 Feb 2010 11:31:34 -0500")
Message-ID: <87iq26mru2.fsf@raven.defaultvalue.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: list

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