Re: [notmuch] Threading

2010-01-14 Thread martin f krafft
also sprach Carl Worth cwo...@cworth.org [2010.01.15.1108 +1300]:
  Reading is one thing. Information storage and organisation is
  another. After a message is delivered (and read) to my mailbox,
  it's really mine and I can (and should be able) to affix it and
  integrate it into my organisational scheme any way I want, don't
  you think?
 
 A fair point.
 
 I don't see this being something I'm going to spend any time
 implementing. I just wouldn't use the functionality myself. But
 I would be happy to integrate patches if someone came up with
 some.

Maybe I should try to persuade you in person.

Just today I referenced a discussion I had with a client's ISP,
which was done via a web-based support system (custhelp.com). They
send you e-mail for every post you or they make to the thread, but
those e-mails do not reference each other. Fortunately, I stitched
them together and when I searched for the correspondence in my
mailstore, I had the entire thread available to me, which was handy
(thanks to mutt's useful thread handling abilities).

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
this week dragged past me so slowly;
 the days fell on their knees...
-- david bowie
 
spamtraps: madduck.bo...@madduck.net


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: [notmuch] Threading

2009-12-15 Thread Marten Veldthuis
On Thu, 10 Dec 2009 13:30:13 -0800, Carl Worth cwo...@cworth.org wrote:
 But I still have a hard time justifying user operations to manipulate
 threading. The whole point of threading is to make it faster to process
 and read messages. But manual operations like joining and splitting
 threads seem like the user just doing more work, and that *after* having
 read the messages. So that seems mostly backwards to me.

By the way, Outlook  Exchange suck (or at least some versions do), and
don't seem to generate In-Reply-To and References: headers. Just got a
mail which prompted me to write this mail. I'd really like to be able to
join messages in a case like this.

-- 
- Marten
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: [notmuch] Threading

2009-12-10 Thread Carl Worth
On Wed, 9 Dec 2009 16:21:34 -0700, Mark Anderson markr.ander...@amd.com wrote:
 I was wondering if there's a way in notmuch to group un-associated
 threads into a single thread.

There's certainly nothing like that in notmuch currently.

Sup had user-level functionality in the interface for stitching messages
into a single thread, and I definitely think that that doesn't make any
sense.

 I have a bug tracking system that doesn't give me emails that thread 
 naturally in notmuch.

I've seen similar things. Bugzilla emails at least all group into a
single thread in notmuch, but don't get nested correctly at all, and
that's really annoying.

 I wouldn't mind writing a filter that could help identify a thread id
 which should apply to a message, and suggest that to notmuch.

I think the right answer here is to fix the input that notmuch is
getting. Just ensure that each message has a proper In-Reply-To header
and all should be fine. If you can't fix the bug-tracking system to emit
proper email, can you apply your filter and rewrite the message as part
of delivery (before notmuch sees it)?

-Carl


pgp2IZfAgQCpG.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: [notmuch] Threading

2009-12-10 Thread Marten Veldthuis
On Thu, 10 Dec 2009 09:39:48 -0800, Carl Worth cwo...@cworth.org wrote:
 I think the right answer here is to fix the input that notmuch is
 getting. Just ensure that each message has a proper In-Reply-To header
 and all should be fine.

On a related note, what about communicating with people who press reply
on an existing message, change the subject and start a new mail
thread. Most mail clients will still insert the In-Reply-To header,
which in this case is just wrong.

Ofcourse, it's their fault, but one can't educate the entire world. Is
there anything like mutt has, to break a thread at the current message?

-- 
- Marten
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch