[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texinfo-6.8.90 pretest

From: Patrice Dumas
Subject: Re: texinfo-6.8.90 pretest
Date: Fri, 21 Oct 2022 15:18:06 +0200

On Fri, Oct 21, 2022 at 01:53:12PM +0100, Gavin Smith wrote:
> On Thu, Oct 20, 2022 at 04:42:45PM +0200, Patrice Dumas wrote:
> > It could also be possible to accept more commands in @w without giving a
> > warning.
> Given that @footnote and @verb don't work properly inside @w and the
> using @pxref inside @w isn't something that document authors particularly
> want to do, and that the nesting only issues a warning not an error,
> so it will not actually break any documents, just warn the authors, then
> I think it is fine to keep all the warnings as they are.


> Patrice, is there a need for the contain_simple_text flag in
> command_data.txt?  I see in ParserNonXS.pm other commands have
> this hard-coded, e.g. @shortcaption and @math - the same in
> Texinfo/XS/parsetexi/parser.c (check_valid_nesting).
> It would seem like a simple change to treat @w the same as @shortcaption
> and @math here.

It is probably the converse that would be best, that is add
contain_simple_text to shortcaption and math...  Actually,
it would probably be clearer if all the BRACE_arguments commands
that are not contain_plain_text had contain_simple_text explictely.
And also probably the same for line commands.  I am a bit cautious not
to add too many flags, but it would seem nice to me if there were more
contain_* and in_* as flags, as the static table in command_data.txt is
much easier to read than the corresponding codes with all the
conditionals, in my opinion.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]