Gavin Smith [2022-09-17 18:38:16] wrote:
> On Wed, Sep 14, 2022 at 10:13:26AM -0400, Stefan Monnier wrote:
>> I need my scripts to work with "old" makeinfo as well, so that wouldn't
>> help me for the foreseeable future, I'm afraid.
>> Thanks for the expl
> Have you tried the -I option?
I had not, but I just tried and that doesn't help: apparently when
the file starts with "." it's not searched along the list of include
directories but only relative to pwd (whereas I'd need it to look
relative to the includer's directory).
Stefan
> Right now, I can't think of a way to make this happen. The only
> thing I can think of would be to change the code to consider that
> only paths with leading . are considered differently.
Actually, from where I stand, what would make more sense is to make it
so file names that start with . or .
> It is because includes with leading . or .. in their paths in or include
> that are absolute paths are treated differently from other includes:
> they are not searched for in include directories.
[...]
> Unless I missed something, none of these two information is documented.
Hmm... here I was, t
There's something I don't understand about @include:
Say, I have:
doc/foo.texi
doc/gpl.texi
bar.texi
if my `foo.texi` has
@include gpl.texi
@include ../bar.texi
I will be able to use successfully both
cd doc; makeinfo --no-split foo.texi -o ../foo.info
will work fin
I'm working on a new (academic) language and would like to write its doc
in Texinfo, but part of the doc should be formal typing rules, which are
traditionally typeset in LaTeX with things like \frac (or other ways to
get similar "derivation rules"). What would be my best option in
Texinfo? I can
