[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ":" in Scheme names.

From: Eli Zaretskii
Subject: Re: ":" in Scheme names.
Date: Thu, 07 Nov 2002 18:29:43 +0300

> From: Aubrey Jaffer <address@hidden>
> Date: Wed,  6 Nov 2002 22:39:03 -0500 (EST)
>  | However, I don't think it will work to rely on whitespace after the
>  | colon: whitespace is generally ignored by the Info readers when
>  | they look for node names and other keywords.  Likewise, TABs and
>  | SPACEs (and newlines as well) are treated the same.
> When I interpose a newline in an index entry, /usr/bin/info can still
> index it, but Emacs says "Info-index: No `make-color' in index".

That's a misunderstanding: I meant the whitespace in the Info file,
not in its Texinfo source.  In the source, the "@cindex foo" entry
_must_ be a single line.

>  | These assumptions are buried deep inside the low-level search
>  | routines of the Info reader, which don't really know whether they
>  | are looking for an index entry or something else, so it's not easy
>  | to change that.
> You just said there are many info readers -- so the difficulty you
> cite with "the Info reader" will not apply to all readers.

It applies to the reader that's part of the Texinfo package.  Clearly,
whatever change we make should not break that reader.

>  |  * mkfifo: (fileutils)mkfifo invocation.         Create FIFOs: (named 
> pipes).
>  | 
>  | There are two colons with whitespace after them here; how do you
>  | tell Info which one to take as the significant delimiter?  The part
>  | to the right of the node name is free text, so anything can go
>  | there.
> The DIR file is not an index.

It's a menu.  The index is also a menu.  An Info reader doesn't know
whether the menu it's looking at is an index or just a menu.  So
whatever changes we do, they will affect menus as well as indices.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]