On Wed, 15 Sep 2010 19:53:41 -0500, Rob Browning wrote:
> 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 (
On Wed, 15 Sep 2010 19:53:41 -0500, Rob Browning
wrote:
> 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
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 tri
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 tri
Hi, folks. I'm continuing to find it problematic that duplicate
messages are only appearing to be indexed once. I'm wondering what are
the possbile solutions to this issue, if any.
For instance, I sent a message that was bcc'd to a long list of people,
including myself. All of my sent mail is f
Hi, folks. I'm continuing to find it problematic that duplicate
messages are only appearing to be indexed once. I'm wondering what are
the possbile solutions to this issue, if any.
For instance, I sent a message that was bcc'd to a long list of people,
including myself. All of my sent mail is f
On Fri, 05 Feb 2010 11:31:34 -0500, Jameson Rollins wrote:
> I'm noticing that notmuch is either not syncing, or not returning in
> searches, duplicate messages that have identical bodies but different
> headers.
This is indeed the correct behaviour of notmuch. There has been some
discussion on i
On Fri, 05 Feb 2010 14:47:03 -0500, Jameson Rollins wrote:
> On Fri, 05 Feb 2010 14:39:22 -0500, micah anderson
> wrote:
> > Welcome to how gmail does it.
>
> Why welcome me to "how gmail does it"?! I never wanted to go there!
Because the perception of the internet by the third larges mail pr
On Fri, 05 Feb 2010 14:39:22 -0500, micah anderson wrote:
> Welcome to how gmail does it.
Why welcome me to "how gmail does it"?! I never wanted to go there!
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 83
On Fri, 05 Feb 2010 12:49:21 -0500, Jameson Graef Rollins wrote:
> A policy of only returning one is going to be problematic for folks who
> want or expect to see the other. And in fact think I want to see both.
> I have both, and I've asked notmuch to index both, so why shouldn't it
> return bo
On Fri, 05 Feb 2010 14:47:03 -0500, Jameson Rollins
wrote:
> On Fri, 05 Feb 2010 14:39:22 -0500, micah anderson wrote:
> > Welcome to how gmail does it.
>
> Why welcome me to "how gmail does it"?! I never wanted to go there!
Because the perception of the internet by the third larges mail prov
On Fri, 05 Feb 2010 18:25:59 +0100, Marten Veldthuis
wrote:
> This is indeed the correct behaviour of notmuch. There has been some
> discussion on it in the past, I believe with proposals to track both
> messages and show only one; but I don't think I've seen proponents of
> showing both duplicat
On Fri, 05 Feb 2010 14:39:22 -0500, micah anderson wrote:
> Welcome to how gmail does it.
Why welcome me to "how gmail does it"?! I never wanted to go there!
pgpoMWddEH8eD.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.or
On Fri, 05 Feb 2010 12:49:21 -0500, Jameson Graef Rollins
wrote:
> A policy of only returning one is going to be problematic for folks who
> want or expect to see the other. And in fact think I want to see both.
> I have both, and I've asked notmuch to index both, so why shouldn't it
> return b
Hey, folks. I'm noticing a somewhat problematic behavior of notmuch
that I was wondering if anyone could comment on.
I'm noticing that notmuch is either not syncing, or not returning in
searches, duplicate messages that have identical bodies but different
headers. This comes up when I send messa
On Fri, 05 Feb 2010 18:25:59 +0100, Marten Veldthuis
wrote:
> This is indeed the correct behaviour of notmuch. There has been some
> discussion on it in the past, I believe with proposals to track both
> messages and show only one; but I don't think I've seen proponents of
> showing both duplicat
On Fri, 05 Feb 2010 11:31:34 -0500, Jameson Rollins
wrote:
> I'm noticing that notmuch is either not syncing, or not returning in
> searches, duplicate messages that have identical bodies but different
> headers.
This is indeed the correct behaviour of notmuch. There has been some
discussion on
Hey, folks. I'm noticing a somewhat problematic behavior of notmuch
that I was wondering if anyone could comment on.
I'm noticing that notmuch is either not syncing, or not returning in
searches, duplicate messages that have identical bodies but different
headers. This comes up when I send messa
18 matches
Mail list logo
