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
On Tue, Sep 13, 2022 at 08:14:48PM -0400, Stefan Monnier wrote:
>
> 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
> 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
> 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 .
On Wed, Sep 14, 2022 at 10:16:16AM -0400, Stefan Monnier wrote:
> > 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, wha
On 9/13/22 17:14, Stefan Monnier wrote:
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 --
> 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
On Thu, Sep 15, 2022 at 03:35:26PM -0400, Stefan Monnier wrote:
> > 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
On Thu, Sep 15, 2022 at 10:17:43PM +0200, Patrice Dumas wrote:
> On Thu, Sep 15, 2022 at 03:35:26PM -0400, Stefan Monnier wrote:
> > > 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
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 explanation, tho. It confirms that I'll have to
> workaround the problem some other way.
You
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 explanation, tho. It confirms that I'll have to
11 matches
Mail list logo
