From: "Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu>
Cc: karl@freefriends.org
Subject: Re: Invisible colons in Emacs Info.
Date: Mon, 07 Jul 2003 10:47:54 -0400 [thread overview]
Message-ID: <200307071447.h67ElsGB015781@rum.cs.yale.edu> (raw)
In-Reply-To: 200307062342.h66Ngvs08232@raven.dms.auburn.edu
> So, in other words, the importance of putting a space after the first
> Mtools is really to make clear that this is where the real subtopic
> name ends. The reason why Karl and me would like to insist on the
> space after the final colon is not: "Because we tell so!", but to make
> clear that the final colon is really the final colon and to avoid
> confusion in cases like this one.
I don't know what makes you think that this hasn't been clear, but
just in case: yes we all agree about that (including the regexp, AFAIK).
> Actually, let us take a look at the actual menu entry which does have
> the space we want:
>
> * Mtools: (mtools). Mtools: utilities to access DOS disks in Unix.
>
> I do not know whether you have this entry and hence can check the
> following:
>
> Put the cursor on that line and do `m'.
>
> Look at the echo area:
Nitpick: this is not the echo area but the minibuffer.
The reason why I'm nitpicking here is because you also referred to the echo
area in the other email and I thought you were referring the help-echo
property (which is the only thing appearing in the echo area).
> Menu item (default Mtools: (mtools). Mtools):
It looks like a bug due to the fact that this part of the code had its
own idea of what is a valid menu entry name. The bug was
introduced several months ago along with the patch that allowed `:'
in menu entries. See patch below.
Stefan
--- info.el.~1.364.~ Sun Jul 6 13:01:11 2003
+++ info.el Mon Jul 7 10:44:54 2003
@@ -1652,7 +1652,9 @@
(save-excursion
(goto-char p)
(end-of-line)
- (if (re-search-backward "\n\\* +\\([^\t\n]*\\):" beg t)
+ (if (re-search-backward (concat "\n\\* +\\("
+ Info-menu-entry-name-re
+ "\\):") beg t)
(setq default (match-string-no-properties 1))))))
(let ((item nil))
(while (null item)
next prev parent reply other threads:[~2003-07-07 14:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 22:43 Invisible colons in Emacs Info 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 [this message]
2003-07-08 2:17 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-07-06 23:56 Karl Berry
2003-07-07 0:47 ` Luc Teirlinck
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-06-25 21:04 Karl Berry
2003-06-25 20:00 Karl Berry
2003-06-25 19:58 Karl Berry
2003-06-25 20:12 ` Luc Teirlinck
2003-06-25 2:34 Luc Teirlinck
2003-06-25 2:45 ` Luc Teirlinck
2003-06-25 17:52 ` Stefan Monnier
2003-06-25 18:49 ` Luc Teirlinck
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
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=200307071447.h67ElsGB015781@rum.cs.yale.edu \
--to=monnier+gnu/emacs@cs.yale.edu \
--cc=karl@freefriends.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).