From: Didier Verna <didier@epita.fr>
Subject: the balloon-help specifier problem.
Date: 28 Dec 1999 19:35:32 +0100 [thread overview]
Message-ID: <muxpuvqkj63.fsf@uzeb.lrde.epita.fr> (raw)
I think I've found why Lars attempted to turn the %< %> format specs
into something else, corrently broken. Indeed, the < and > characters are now
used in the /summary/ line format with the following meaning:
,----
| `>'
| One space for each thread level.
|
| `<'
| Twenty minus thread level spaces.
`-----
I'd prefer to keep them for the balloon-help property as before,
because they constitute an open/close set, like [] () and {}, all already
taken. What do you think ? What could we use instead ? Obviously, keeping the
current ones, which are non ascii (« and ») is out of question.
--
/ / _ _ Didier Verna http://www.inf.enst.fr/~verna/
- / / - / / /_/ / EPITA / LRDE mailto:didier@epita.fr
/_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77
94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99
next reply other threads:[~1999-12-28 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-28 18:35 Didier Verna [this message]
2000-01-11 12:15 ` Toby Speight
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=muxpuvqkj63.fsf@uzeb.lrde.epita.fr \
--to=didier@epita.fr \
/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).