Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: trn trees
Date: 09 Jan 1996 19:02:25 +0100	[thread overview]
Message-ID: <ybrhz1ou.fsf@bjob.no> (raw)

Well, I finally wrote that trn thread tree thingie:

----------
[***]~(   )-[odd]-[Gun]
     |     \[Jan]
     |     \[odd]-[Eri]
     |     \(   )-[Eri]
     |           \[odd]-[Paa]
     ~(   )-(   )-(   )-(   )-[Joh]-[Bjo]
     |     |                       \[Roa]-[Bjo]
     |     |                       \[YuN]
     |     \(   )-(   )-(   )-(   )-[Ste]-[Tho]
     |                             \(   )-[Ste]-[Bjo]
     |                                         \[Roa]
     ~[Gun]-[Bjo]
----------

That looks very ugly, so it'll probably not look like that.   The
nodes and the lines and everything is (of course) controlled by those
format-like variables we all know and love.  (Uhm.)

The "~" things means that the "[***]" article is a false root.  The 
"(   )" articles are the result of filling in missing articles in the
threads.  (I've called this "sparse threads" for some reason or
other.)  

I've done a new mode called `gnus-tree-mode', and you can use
absolutely all summary mode commands in that mode.  You can display
the summary mode and the tree mode at the same time, or just use the
tree mode buffer to navigate in.  Or just the article mode buffer --
I've finally ironed out the problems with that as well, I think.

Gosh!  The ChangeLog entries since the 0.26 release is 12k long.
Which means that I must have introduced *tons* of new bugs.  :-)  

-- 
   Lars Magne Ingebrigtsen * larsi@ifi.uio.no
      (a red leaf that falls from the purple tree)


             reply	other threads:[~1996-01-09 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-09 18:02 Lars Magne Ingebrigtsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-01-04  6:36 Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ybrhz1ou.fsf@bjob.no \
    --to=larsi@ifi.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).