unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Invisible colons in Emacs Info.
Date: Fri, 27 Jun 2003 19:36:21 -0500 (CDT)	[thread overview]
Message-ID: <200306280036.h5S0aLm19442@eel.dms.auburn.edu> (raw)
In-Reply-To: <200306252112.h5PLCiko007276@rum.cs.yale.edu> (monnier+gnu/emacs@cs.yale.edu)

We probably need a decision on the following issue:

It seems that the current de facto situation for menu subtopic names
is the following:

1.  They can contain colons, but not colons followed by a space.
2.  There must be at least one space separating the subtopic name and
    the node name.

If this is considered OK, then nothing needs to be done.  

Some, like Karl, would prefer not to allow colons at all until a new
syntax for quoting node names is introduced in Texinfo.  That would
also be easy, one would just have to revert earlier changes.

Stefan and Karl pointed out that condition 2 used not to be
necessary.  There seems to be some doubt as to whether its
introduction was deliberate or accidental.

If we want 1.  but not 2. then things become much more complicated and
precise specs would need to be agreed upon.

Quoting Stefan, who proposed an (if I understand correctly) admittedly
non-ideal patch:

   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.  If anybody wants to spice up the
   Info-menu-entry-name-re regexp accordingly...
   We really need a better solution.

Sincerely,

Luc.

  parent reply	other threads:[~2003-06-28  0:36 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
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 [this message]
  -- 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=200306280036.h5S0aLm19442@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).