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: Wed, 25 Jun 2003 15:12:15 -0500 (CDT)	[thread overview]
Message-ID: <200306252012.h5PKCFQ16805@eel.dms.auburn.edu> (raw)
In-Reply-To: <200306251958.h5PJwor30121@f7.net> (karl@freefriends.org)

Karl Berry wrote:

       blame me if you disagree) very much want to support entries like:
       * menu:entry:  entry.       description.

   To what end?  I mean, what are the real examples that are hoped to be
   supported?  This is new Info syntax, as far as I know.  If makeinfo
   doesn't complain about it, it probably should.

   I don't understand even this skeletal example.  Surely the point here is
   not to repeat the node name `entry', that wouldn't be useful.  

The concrete names are irrelevant:

* text1:text2:   text3.   text4.

>From info.el:

;; Note that nowadays we expect info files to be made using makeinfo.
;; In particular we make these assumptions:
;;  - a menu item MAY contain colons but not colon-space ": "
;;  - a menu item ending with ": " (but not ":: ") is an index entry
;;  - a node name MAY NOT contain a colon
;; This distinction is to support indexing of computer programming
;; language terms that may contain ":" but not ": ".

This text clearly wants to support menu items like:

* text1:text2:     text3.   text4.

(Unless I misunderstood, sorry for the confusion in that case.)

I thought I understood from previous messages that you "agreed to
disagree" with people who held the views expressed above.  (Or am I
completely misunderstanding things?)

Sincerely,

Luc.

  reply	other threads:[~2003-06-25 20:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 19:58 Invisible colons in Emacs Info Karl Berry
2003-06-25 20:12 ` Luc Teirlinck [this message]
  -- 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-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  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=200306252012.h5PKCFQ16805@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).