Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: the balloon-help specifier problem.
Date: 11 Jan 2000 12:15:30 +0000	[thread overview]
Message-ID: <uvh50249p.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: Didier Verna's message of "28 Dec 1999 19:35:32 +0100"

dv> Didier Verna <URL:mailto:didier@epita.fr>

0> In article <muxpuvqkj63.fsf@uzeb.lrde.epita.fr>, dv wrote:

dv> I think I've found why Lars attempted to turn the %< %> format
dv> specs into something else, corrently broken. Indeed, the < and >
dv> characters are now used in the /summary/ line format with the
dv> following meaning:
dv>
dv>  ,----
dv> | `>'
dv> |      One space for each thread level.
dv> |
dv> | `<'
dv> |      Twenty minus thread level spaces.
dv> `-----
dv>
dv> I'd prefer to keep them for the balloon-help property as before,
dv> because they constitute an open/close set, like [] () and {}, all
dv> already taken.  What do you think?

When they were introduced for the balloon-help, some sort of replacement
for their existing use as thread indentation should have been provided.
Either that, or the balloon-help should have used something not already
taken.

This has bitten me several times, and it doesn't get any less annoying.

BTW, if we're going to change the thread-depth-spaces format specifiers,
can I suggest using some sort of matched pair - e.g. a lowercase/uppercase
pair of letters.  And it will need a NEWS entry as a user-visible change.




      reply	other threads:[~2000-01-11 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-28 18:35 Didier Verna
2000-01-11 12:15 ` Toby Speight [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=uvh50249p.fsf@lanber.cam.eu.citrix.com \
    --to=toby.speight@streapadair.freeserve.co.uk \
    /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).