Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Matts (1087)

Matts
  (email not shown publicly)

I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Thursday November 02, 2006
07:43 PM

Pine perfected

[ #31492 ]

For a while I've been using pine 4.64 and the fancy threading features. Not being a fan of full threads (it's easy to lose track of the flow when your mailer is busy trying to display it all as a tree structure - I guess this is part of the appeal of gmail "conversations") I use OrderedSubject, as it's very similar to what Mail.app provides me, a style of threading that I like very much.

But pine's was annoyingly different - it would sort the message view by order of the first mail in the thread, rather than by the most recent mail in the thread, causing replies to old threads to be way off my main screen (and thus me missing said replies).

However today I found the fancy threading patch to pine, which fixes that (as an option). So I'm a happy camper today.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • yeah, this is one failing of the "traditional" threading algorithm as described by JWZ at http://www.jwz.org/doc/threading.html [jwz.org] .

    what I did in 'mhthread' (despite what the POD says ;) is the following, from a comment:

    > Sort by the date of the earliest message with that subject line. However:
    > if messages share a subject line, but don't refer to each other using IRT
    > or Refs headers, and were posted far enough apart (greater than 24 hours),
    > then don't thread them consecutively; allow other thre
    • Yeah, but that still means a new message to an older thread goes higher up the screen.

      I wanted Mail.app's design - all new messages go to the to bottom of the screen, attached to their thread.
      • oh I see what you mean; the entire thread is moved to match the newest message's location. hmm, I may have to hack that.