On 25 Feb 2022 16:06, Karl Berry wrote:
> Adding a note to the manual is fine, but what would be (much) more
> likely to actually get noticed by users is a runtime warning. What is
> the actual behavior when the basename and @setfilename don't match?
i don't think it's possible to detect from auto
On Fri, Feb 25, 2022 at 04:29:11PM -0700, Karl Berry wrote:
> Runtime warning in texi2any or automake?
>
> Both?
It seemed to me that @setfilename in texi2any was actually a way to
have an output file name different from the input file name. If this is
not really useful, we should simply ign
Runtime warning in texi2any or automake?
Both?
On Fri, Feb 25, 2022 at 04:06:34PM -0700, Karl Berry wrote:
> Adding a note to the manual is fine, but what would be (much) more
> likely to actually get noticed by users is a runtime warning. What is
> the actual behavior when the basename and @setfilename don't match?
> Sorry to be clueless ...
Adding a note to the manual is fine, but what would be (much) more
likely to actually get noticed by users is a runtime warning. What is
the actual behavior when the basename and @setfilename don't match?
Sorry to be clueless ...
On Thu, Feb 24, 2022 at 10:32:20PM -0500, Mike Frysinger wrote:
> > The only issue I see is if after the
> > file is generated the @setfilename is not the same as the file base name
> > there will be errors. I do not think that automake should support that
> > setup, but maybe it would be good to
