Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@metis.no>
Subject: Indicating hidden threads (Was: Improved (non-annoying) ...)
Date: 17 May 2000 17:36:17 +0200	[thread overview]
Message-ID: <whk8gtrxxq.fsf_-_@viffer.metis.no> (raw)
In-Reply-To: Bill White's message of "17 May 2000 06:41:17 -0500"

>>>>> Bill White <billw@wolfram.com>:

> The new default is rather annoying when a style other than underlining
> is used. See <url:http://members.wri.com/billw/underlining.jpg> (150Kb)

Hm... it looks like you have some indications on hidden threads in
your summary buffer: the "+" on the left hand side and the "|-->" to
the right.

Is this something you have modified yourself (eg. a different format
for the Summary buffer)?  Or is this something that is easily turned
on?  When I do
	T h
I see no such marks.

I really like this behaviour in Forté Free Agent and Netscape, and
wouldn't mind seeing it in my Gnus.  Hm...
	C-h i g (gnus)Summary Buffer Lines RET

Hm... looks like the "+" is just a score indicator.  What about the
"|-->" then?  I didn't find anything matching in the above node.  This 
is the closest I got:

`e'
     An `=' (`gnus-not-empty-thread-mark') will be displayed if the
     article has any children.




  parent reply	other threads:[~2000-05-17 15:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-16 21:19 Improved (non-annoying) underlining Karl Kleinpaste
2000-05-16 22:03 ` Shenghuo ZHU
2000-05-17 11:41 ` Bill White
2000-05-17 12:09   ` Per Abrahamsen
2000-05-17 12:26     ` Hrvoje Niksic
2000-05-17 15:37       ` Steinar Bang
2000-05-17 12:29     ` Karl Kleinpaste
2000-05-17 12:39       ` Hrvoje Niksic
2000-05-17 12:58         ` Karl Kleinpaste
2000-05-17 13:35           ` François Pinard
2000-05-17 13:55           ` Kai Großjohann
2000-05-17 14:03             ` Karl Kleinpaste
2000-05-17 14:27               ` Alan Shutko
2000-05-17 14:40               ` Kai Großjohann
2000-05-17 14:42                 ` Karl Kleinpaste
2000-05-17 16:00                   ` Yair Friedman (Jerusalem)
2000-05-17 14:08           ` Karl Kleinpaste
2000-05-17 14:32             ` Shenghuo ZHU
2000-05-17 14:29           ` Toby Speight
2000-05-17 15:22           ` Yair Friedman (Jerusalem)
2000-05-19  0:22           ` Russ Allbery
2000-05-19  1:41             ` Karl Kleinpaste
2000-05-19  2:09               ` Dan McGuirk
2000-05-19  4:56               ` Russ Allbery
2000-05-17 13:30   ` François Pinard
2000-05-17 14:28     ` Bill White
2000-05-17 14:33       ` Bill White
2000-05-17 14:34         ` Karl Kleinpaste
2000-05-17 18:05         ` Per Abrahamsen
2000-05-17 15:36   ` Steinar Bang [this message]
2000-05-17 16:07     ` Indicating hidden threads (Was: Improved (non-annoying) ...) Bill White
2000-05-17 20:13       ` Steinar Bang
2000-05-20  9:26         ` Rade Markovic

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=whk8gtrxxq.fsf_-_@viffer.metis.no \
    --to=sb@metis.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).