From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Invisible colons in Emacs Info.
Date: Wed, 25 Jun 2003 13:49:15 -0500 (CDT) [thread overview]
Message-ID: <200306251849.h5PInF016695@eel.dms.auburn.edu> (raw)
In-Reply-To: <200306251752.h5PHqcTi006187@rum.cs.yale.edu> (monnier+inbox@cs.yale.edu)
Stefan Monnier wrote:
In nornal menus, things look like:
* menu:entry. description.
whereas in indices, the description is missing and things look like:
* menu: entry.
note the clever use of he fact that whitespaces between `menu:'
and `entry.' is ignored.
But the question is: how does that difference have anything to do with
whether or not colons should be hidden?
On another note, the whitespace is ignored by makeinfo and the
stand-alone Info reader, but not by Emacs. In Emacs
* menu: entry description.
will visit entry, but
* menu:entry. description.
will yield an error. It does not matter if one replaces "menu" by
some less ambiguous name. The stand-alone Info visits entry.
Emacs insists on the space after the colon, because it wants to
support colons in the middle of menu subtopic names.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-06-25 18:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 2:34 Invisible colons in Emacs Info Luc Teirlinck
2003-06-25 2:45 ` Luc Teirlinck
2003-06-25 17:52 ` Stefan Monnier
2003-06-25 18:49 ` Luc Teirlinck [this message]
2003-06-25 18:56 ` Stefan Monnier
2003-06-25 18:59 ` Luc Teirlinck
2003-06-25 19:04 ` Luc Teirlinck
2003-06-25 19:13 ` Luc Teirlinck
2003-06-25 19:25 ` Luc Teirlinck
2003-06-25 19:58 ` Luc Teirlinck
2003-06-25 21:12 ` Stefan Monnier
2003-06-25 21:26 ` Luc Teirlinck
2003-06-28 0:36 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-06-25 19:58 Karl Berry
2003-06-25 20:12 ` Luc Teirlinck
2003-06-25 20:00 Karl Berry
2003-06-25 21:04 Karl Berry
2003-07-01 0:03 Karl Berry
2003-07-01 0:31 ` Luc Teirlinck
2003-07-04 0:12 ` Stefan Monnier
2003-07-05 3:14 ` Luc Teirlinck
2003-07-05 18:28 ` Robert J. Chassell
2003-07-06 13:49 ` Kim F. Storm
2003-07-06 13:03 ` Robert J. Chassell
2003-07-06 18:17 ` Luc Teirlinck
2003-07-06 18:27 ` Luc Teirlinck
2003-07-06 19:19 ` Luc Teirlinck
2003-07-06 23:38 ` Kim F. Storm
2003-07-05 13:15 ` Luc Teirlinck
2003-07-06 22:43 Karl Berry
2003-07-06 22:58 ` Luc Teirlinck
2003-07-06 23:07 ` Stefan Monnier
2003-07-06 23:42 ` Luc Teirlinck
2003-07-07 14:47 ` Stefan Monnier
2003-07-08 2:17 ` Luc Teirlinck
2003-07-06 23:56 Karl Berry
2003-07-07 0:47 ` Luc Teirlinck
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200306251849.h5PInF016695@eel.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).