> I don't mind having an indication for m4 usage in a comment line of
> its own. But combining it with an Emacs Local Variable line or
> section sounds really bad.
Oops, the last sentence might be ambiguous. Please add
... if you don't follow the convention for Local Variables.
Werner
> whatever the macro argument is) with the old and the new
> texinfo.tex version.
>
> Do you know one?
>
> No. The only way I see to retain compatibility with the 4.13
> texinfo.tex is not to use @macro when the arg might have \. Sorry.
Sigh. This is *really* disappointing! Well
> Sounds reasonable. However, if you do that, m4 *must* become part of
> TeXLive!
>
> Gee. I totally disagree! It is not TL's business to provide system
> utilities. The resulting conflicts are a true pain. Even getting it to
> build on our all platforms, in a way that works in the bu
I'm all for it!
Thanks :).
Using m4 as preprocessor will make Texinfo extremely powerful.
That's what I was thinking too :).
The default quotes should perhaps be redefined, because ``..'' used in
Texinfo would conflict with them.
Right, sigh. I had forgotten that m4 stripped
whatever the macro argument is) with the old and the new texinfo.tex
version.
Do you know one?
No. The only way I see to retain compatibility with the 4.13
texinfo.tex is not to use @macro when the arg might have \. Sorry.
k
What about implementing a solution with luatex? Would that work?
No. I mean, sure, it could work for people using luatex, but
a) luatex will be a moving target for quite some time to come, and
b) a vanishingly small percentage of people use it, and
c) it would take quite a lot of development
> Regarding macros in general. I've been trying, and I have become
> skeptical that there is any way to devise a new Texinfo macro
> command that does not run afoul of many of the same issues. In
> particular, TeX cannot precisely control behavior at newlines, and
> newline-delimited commands ar
> Well, with texinfo.tex from 4.13 `\q' works, with current CVS it
> doesn't.
>
> Ok, now I'm totally baffled. Maybe \ never acted as a quote char
> back then?
No idea :-) I only see an incompatible change in texinfo.tex, for
whatever reasons. Unfortunately, I haven't yet found a solut
> "AM" == Alan Mackenzie writes:
AM> I'm running on a newish, up to date Gentoo Gnu/Linux system. I type:
AM> $ texi2dvi -V --tidy cc-mode.texi
AM> and it fails to produce output or give an error message.
AM> It seems I am lacking a font called "lcircle10".
lcircle10.{mf,tfm} are in
Karl Berry ha escrit:
> Patrice and I haven't had a chance to discuss this in detail yet, but at
> present it seems to me that the most robust plan would be to simply
> provide an option to run the document through m4 before Texinfo.
I'm all for it! Using m4 as preprocessor will make Texinfo ext
10 matches
Mail list logo
