From: "Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Invisible colons in Emacs Info.
Date: Thu, 03 Jul 2003 20:12:34 -0400 [thread overview]
Message-ID: <200307040012.h640CY1B015117@rum.cs.yale.edu> (raw)
In-Reply-To: 200307010003.h6103d623188@f7.net
> Stefan and Karl pointed out that condition 2 used not to be necessary
>
> And condition 1 did not obtain; colons were not allowed.
I thought the idea was to allow colons such that previously invalid
entries (with colons) are now allowed. I think previously valid
entries should stay valid.
> If we want 1. but not 2. then things become much more complicated and
> precise specs would need to be agreed upon.
>
> 1-but-not-2 requires the "real fix" or "better solution" or whatever you
> want to call it, as far as I can tell. (Quoting syntax.)
>
> Problem is that it still fails on:
>
> * name1:foo:node. des:cription.
>
> because it thinks the menu entry name is "name1:foo:node. des"
> and the node name is "cription". I'm sure we can tune the disambiguation
> by saying that menu entries can have `:' but cannot have `.' after the `:'
> or some other such heuristic.
>
> Huh? According to the rule above, the above is invalid because it lacks
> a space, right?
Indeed, it's not a big deal: it was not valid before and it's not
valid now either. It's thus a non-issue. Sorry for not noticing it.
> If that's what you were saying.
> It's simpler both to understand and to implement to just require :<space>
> as a separator. Or :<tab>, I suppose.
Well, actually my regexp implementation is simpler than the hand-parsing code
that was used before, AFAICT.
Stefan
next prev parent reply other threads:[~2003-07-04 0:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 0:03 Invisible colons in Emacs Info Karl Berry
2003-07-01 0:31 ` Luc Teirlinck
2003-07-04 0:12 ` Stefan Monnier [this message]
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
-- 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-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-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=200307040012.h640CY1B015117@rum.cs.yale.edu \
--to=monnier+gnu/emacs@cs.yale.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).