Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: Pretty thread trees in summary buffer
Date: Wed, 04 Dec 2002 23:47:30 +0100	[thread overview]
Message-ID: <adjlqu4d.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <81el8zlzod.fsf@shasta.cs.uiuc.edu>

Lars Clausen <lrclause@cs.uiuc.edu> writes:

> I see that Oort Gnus has pretty thread trees with little arrows (like Mutt
> and Slrn), and I saw an old patch for Gnus 5.8.3 that doesn't seem to have
> made it into mainstream Gnus.  I'm using Gnu Emacs 21.1.1 and Gnus 5.9.0 on
> a Debian box, and would really like to have pretty threads in the summary
> buffer.  Where should I be looking?

Jump in the cold water and get Oort. Serious it's in many respects
better than 5.8.8 and 5.9 (which are the same) and only heaven knows
when we'll see a release.

Do a checkout from CVS, read gnus.ding for two weeks after that and see
if there are any major bug reports, then make a backup of the checkout,
and do CVS update, read through the changelogs of the last two weeks,
see if something looks like an important bugfix, if not install and use
it. Then you should be quite save from major trouble, at least this
works for me since months now.

-- 
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.


      parent reply	other threads:[~2002-12-04 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <81el8zlzod.fsf@shasta.cs.uiuc.edu>
     [not found] ` <87smxedg44.fsf@sdbk.de>
2002-12-03 20:39   ` Jesper Harder
2002-12-04 22:47 ` Frank Schmitt [this message]

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=adjlqu4d.fsf@hschmi22.userfqdn.rz-online.de \
    --to=usereplyto@frank-schmitt.net \
    --cc=replies@Frank-Schmitt.net \
    /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).