Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: thread tree misdisplays
Date: 10 Jan 1997 16:42:32 -0500	[thread overview]
Message-ID: <vxksp49dx6f.fsf@pocari-sweat.jprc.com> (raw)

I've never used thread trees much before, but I've finally decided I
can use them now.  I've been using a 2-way split for some time, with
*Group* above *Summary* on the left, and the *Article* on the right,
in a very wide (200-column) Xemacs; what is intended now is the
addition of a thread tree display above the *Article*, the same size
as the corresponding *Group* buffer on its left.

	   (gnus-add-configuration
	    '(article
	      (horizontal 1.0
			  (vertical 0.4
				    (group 0.25)
				    (summary 1.0 point))
			  (vertical 1.0
				    (tree 0.25)	; <-- addition here
				    (article 1.0)))))

There are 3 problems with this that I see:

1. The use of boldface font for the names in *Tree* display entries
means that the lines defining the tree branches do not line up with
the entries themselves.  That is, the lines of display connecting
entries are plain-font [-\]* strings, but when one has scored a
subject higher, all the entries are boldfaced, and so the entries
themselves don't line up properly among those plain-font [-\]*
connectivity strings.  Can the font used in the *Tree* buffer be
forced to a plain state in all cases?

2. Again because of boldface (it appears), if the thread is very wide
in *Tree* (very tall in *Summary*), then one can find oneself looking
at an article such that no entry in the visible portion of *Tree* is
highlighted -- the would-be highlighted entry is beyond the right edge
of what the buffer displays.

3. Lastly, if a thread is very tall in *Tree* (very wide in
*Summary*), *Tree* flickers back and forth as one moves from one
article to the next, between showing an entry and then showing the top
line of the *Tree* buffer.  I would think it should move the buffer
down so that the highlighted name is remains visible.

--karl


             reply	other threads:[~1997-01-10 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-10 21:42 Karl Kleinpaste [this message]
1997-01-14 23:39 ` 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=vxksp49dx6f.fsf@pocari-sweat.jprc.com \
    --to=karl@jprc.com \
    /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).