Re: the little thread tree thing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


In article <>,
Matt Ackeret  <> wrote:
>I guess I made up that "tree view" term, I had thought I heard it somewhere
>(presumably this list).

I never knew you could turn it off.  :->

>Well, I don't want it *ON*, since it wastes part of the screen space that
>I don't care about 99% of the time.

What space does it take up?

Consider this post, for instance (I have all of my mailing lists going into
leafnode, so I'm reading this with trn).

The header looks like: (moderated) #17 (1 + 1 more)                (1)--[1]
Newsgroups:,              ( )--(1)--(1)
From: Matt Ackeret <>
[1] Re: the little thread tree thing
Date: Thu Mar 21 11:05:42 PST 2002

That isn't taking up any more space because the headers are already there.

Or did you some how turn off all of those headers too?

>I guess it is inverting the number and parentheses around the number of
>the message I JUST read (or "am reading" if you use the upper right hand

() are marked read
[] are marked unread

>Yeah, but you could/can just "m"ark the message, space-through the rest of
>the thread, and see if anybody answered it.  (At least that's what I currently

That's what I used to do, when I used rn.  Occasionally I still do with trn
if I want to see if anyone else has made the point I'm interested in making.

>So how do I figure out how to READ this thing?  That's why I started this
>question/discussion in the first place.
>For example:
>  (A)+-(B)
>     \-(C)
>I replaced the "1"s with letters.  (and is the # ever anything but 1?)

The numbers change when the subject changes.  Happens if a topic drifts and
someone bothers to change the subject, or some other newsreader truncates

>What is the relationship of A to B to C?  I don't understand what
>horizontally versus "diagonally" means.  I mean, it's something like
>reply to the message specifically rather than just another message
>in the thread.

Well, these posts in mutt (in the original mail archive) would look threaded
like this:

3604 N   Mar 20 Matt Ackeret    (  46) the little thread tree thing
3605 N   Mar 20 Mike Castle     (  49) +->
3606 N   Mar 21 Lars J. Aas     (  38)   +->
3607 N   Mar 21 Lars J. Aas     (  39)     +->
3608 N   Mar 21 Matt Ackeret    (  79)     +->
3609 N   Mar 21 Lars J. Aas     (  27)       +->

(I believe the discrepancies between the trn and mutt tree views is due to
not all of the messages being processed by leafnode yet.)

And are Lars pointed out, the \ is just trying to pretty things up.  It
could also have been done like this:

>  (A)+-(B)
>     +-(C)

>>follow-up, you'll likely want to read the related posts in advance, but
>>avoid reading your way into an unrelated branch or - heaven forbid - end
>unrelated branch?  Wow, that sounds like more "work" reading Usenet than
>I want to get into -- but that's why I'm trying to get explanations/real

Well, consider a thread that looks like this:

   |    \-(D)

Now, you want to reply to B.  By paying attention to the threads, you know,
after reading D, that no one else has replied to B, so you can go back to B
and make your response knowing what everyone else has already said (I did
much the exact same thing responding to THIS post, actually).

>world examples.  I may change my mind.   I mean, I *used* to (argh, I guess
>this was 10 or more years ago) not even like the idea of threaded news,
>because so many people posted unrelated articles in the same thread, so
>just viewing by subject seemed useless..  (Yes, I purposely used "unrelated"
>again, and I know it does more than just by subject, but the subject is
>still part of the process, right?)  Heck, now I even thread email, with pine.

I don't think trn uses Subjects for threading, just the message-ids and
references (maybe in-reply-tos).  Mutt does use Subjects I think, since
dropping references seems to be more prevalent in the email world.

>Basically, this info so far is useful (at least I now know how to
>navigate the tree, I just don't understand what the tree means), and may
>get me used to using another feature of trn.

If the message you are on is highlighted in the tree, that makes things a
LOT nicer.  Are you having any issues with that?

     Mike Castle
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

[Index of Archives]     [Photo]     [Yosemite]     [Epson Inkjet]     [Mhonarc]     [Nntpcache]

  Powered by Linux