On Fri, Oct 16, 2026 at 11:45:03AM +0200, Patrice Dumas wrote:
> On Fri, Oct 16, 2026 at 09:54:34AM +0800, aidan wrote:
> > 1. create a file named "a.texi"
> > 2. run:
> > 
> >     texi2any --set-customization-variable paragraphindent=asis --info a.texi
> > 
> > 3. the following warnings appear:
> > 
> > Argument "asis" isn't numeric in numeric gt (>) at
> > /usr/local/share/texi2any/Texinfo/Convert/ParagraphNonXS.pm line 177.
> > Argument "asis" isn't numeric in numeric ge (>=) at
> > /usr/local/share/texi2any/Texinfo/Convert/PlaintextNonXS.pm line 4042.
> 
> I can reproduce it with the development sources (line numbers changed
> widely, though).  Note that it happens only with pure Perl, with
> TEXINFO_XS=omit.

I found the same.

I noticed that "TEXINFO_XS=omit texi2any --paragraphindent=asis --info a.texi"
still works correctly.  We have special processing of the --paragraphindent
option to convert the argument to the internal value for the paragraphindent
variable.

I don't think it is necessary to make setting 'paragraphindent' to a
keyword argument work as it is a numeric variable internally and the
--paragraphindent option exists.  So one option is just to document the
special values, in case somebody uses this variable: 0 for 'none', -2 for
asis.

Otherwise, it could be slightly complicated to add special handling for
this everywhere the user may set customisation variables: from the
command-line, but also from Perl customisation files.  In
perl/Texinfo/Config.pm, GNUT_set_from_cmdline and texinfo_set_from_init_file
both look relevant (there would also be the XS/C versions, as well).

> I will have a look.
> 
> I am a bit surprised that it does not happen in the test suite, I will
> also have a look if more unit tests could be better.
> 
> Thanks for the report!
> 
> -- 
> Pat
> 

Reply via email to