[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug #42897] texi2any does not bark at incorrect menu entry, and mak
From: |
Gavin Smith |
Subject: |
Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output |
Date: |
Mon, 4 Aug 2014 15:00:32 +0100 |
On Sun, Aug 3, 2014 at 11:07 PM, Vincent Belaïche
<address@hidden> wrote:
> I do not know the info format details --- BTW is it documented somewhere
See "Appendix F Info Format Specification" in the texinfo manual.
> From your answer I see that such kind of escaping mechanism does not
> actually exists (yet ;-) ).
>
> Anyway, I am a bit surprised that there was some effort from people
> doing the EMACS info viewer not to preclude colon in node names, as on
> the other hand they preclude comma albeit the @comma command is already
> there and could be used by the user to have commas in node names. See
> http://savannah.gnu.org/bugs/index.php?42897#comment3.
The @comma command is for commas in the arguments to Texinfo commands,
not for Info output exactly. Commas in node names conflict with the
use of the comma to terminate a cross-reference, or a pointer in the
first line of a node.
Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output, Gavin Smith, 2014/08/01
Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output, Vincent Belaïche, 2014/08/03
- Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output,
Gavin Smith <=