Re: Argument of \\ has an extra } ??
\initial {\\}
As I recall, Arnold and I did that as part of the new texindex, so that
backslashes could be properly sorted, etc. It seems semantically
correct to me. Trying to treat {\tt \indexbackslash } as equivalent
to \ seemed poor design.
(Ultimately, what I really want is for the index files to use @ instead
of \ for the escape character, as should have been done from day one,
but the new texindex has to get far more widely deployed.)
I wonder if there's any way for texindex to output something that is
very likely to work with a bundled texinfo.tex file regardless of
its version.
Of course that would be nice in theory, but barring a kludge like the
above, I don't see how. Perhaps just a failure of imagination. Anyway,
I don't think it is so unreasonable for people to avoid using an ancient
texinfo.tex with the new texindex. If that causes more old
texinfo.tex's to get updated, that's a good thing.
k
P.S.
\gdef\\#1pt{#1}}
Indeed. I wish Knuth hadn't done that (it was one of the last changes
he ever made to plain.tex), but of course it was never up to us and
certainly isn't going to change now.
Re: Argument of \\ has an extra } ??
On 6 July 2015 at 01:42, Norbert Preining prein...@logic.at wrote:
sorry for the noise. The problem lies with octave shipping an ancient
texinfo.tex (2009?).
For what it's worth, I just had the exact same problem trying to
compile an old gawk manual (for gawk 3.1.4), again breaking on a line
\initial {\\}
I wondered if it could be a difference with texindex 6.0. I tried with
texindex 5.2, and the *.cps file contained instead
\initial {{\tt \indexbackslash }}
(The unwanted definition
\gdef\\#1pt{#1}}
comes from line 682 of plain.tex.)
It's unfortunate that compilation of older software packages should be
broken in this way. I wonder if there's any way for texindex to output
something that is very likely to work with a bundled texinfo.tex file
regardless of its version.
Re: Argument of \\ has an extra } ??
On 6 July 2015 at 01:42, Norbert Preining prein...@logic.at wrote:
I had to change two occurrences of
@SOMECMD{\X}
to
@SOMECMD{\\X}
Is this expected?
Yes. See this thread from a few days ago:
https://lists.gnu.org/archive/html/bug-texinfo/2015-07/msg2.html
Re: Argument of \\ has an extra } ??
l.56 \initial {\\}
Works for me with current texinfo.tex and the input below (to force
creating the \initial line). I don't doubt there was a bug in some
version of texinfo.tex in this regard, but I routinely run Texinfo
documents with \indexentries, so I doubt it existed for long. -k
--
\input texinfo
@setfilename backindex.info
@cindex \foo
@cindex bar
@printindex cp
@bye
Re: Argument of \\ has an extra } ??
Hi everyone,
(short: one problem solved, another appeared: @SOMECMD{\X} does not work)
Works for me with current texinfo.tex and the input below (to force
sorry for the noise. The problem lies with octave shipping an ancient
texinfo.tex (2009?). Removing it did bring up two new errors:
As of now there is code like:
alarm character @qcode{\a} to ...
which errored out with
undefined command
I had to change two occurrences of
@SOMECMD{\X}
to
@SOMECMD{\\X}
Is this expected?
In any case, with the above two changes I could fix the building of
the octave texinfo manual.
(@ Octave maintainers: I will send patches (git format-patch) after
I have confirmed that everything is fine now)
All the best
Norbert
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
