unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu>
Cc: karl@freefriends.org
Subject: Re: Invisible colons in Emacs Info.
Date: Sun, 06 Jul 2003 19:07:12 -0400	[thread overview]
Message-ID: <200307062307.h66N7Cen013533@rum.cs.yale.edu> (raw)
In-Reply-To: 200307062258.h66MwJo07540@raven.dms.auburn.edu

> Karl Berry wrote:
> 
>        Mtools:(mtools).        Mtools:
> 
>        a valid subtopic name?
> 
>    According to what we've discussed, that is invalid because the space
>    between the : and the ( is missing.  I thought we had all agreed on this?
> 
> You and me agreed, but I do not believe Stefan ever did.  Otherwise
> there would have been no reason for his recent changes.

My recent change was done for the following reasons:

1 - centralize the definition of what is an acceptable menu entry name
2 - centralize the definition of what is an acceptable node name
3 - get rid of ad-hoc parsing code and use a more declarative style
    using regexps.
4 - accept some old menu entries (that are now considered invalid) as long
    as we can unambiguously recognize them.

I'm fine with labelling menu entries that lack the space after the colon
as invalid, but I see no reason not to tweak the regexp such that we can
still recognize some of those old entries (as long as such tweaking does
not impact valid cases).
My change makes the code accept more cases than what we consider as "valid",
but that seems like a feature rather than a bug since such entries exist
and were valid until Emacs-21.3.  Of course, the priority should be given
to the correct treatment of valid entries.


	Stefan

  reply	other threads:[~2003-07-06 23:07 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 [this message]
2003-07-06 23:42     ` Luc Teirlinck
2003-07-07 14:47       ` Stefan Monnier
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=200307062307.h66N7Cen013533@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).