On Sun, Jan 12, 2025 at 08:28:26PM +0000, Gavin Smith wrote: > On Tue, Jan 07, 2025 at 10:30:22PM +0100, Patrice Dumas wrote: > > Yet another possibility would be to use an environment variable to > > disable the interpreter embedding such that it can be applied very > > early. > > This appears to me to be an implementation detail which you want to > control with a command-line option. This is like the use or non-use > of XS modules, which we control with environment variables (TEXINFO_XS, > TEXINFO_XS_PARSER and others). Hence, it would make sense to me to > also use an environment variable to control the interpreter embedding.
This is implemented with TEXINFO_C_EMBED_PERL being possibly set to 0. This would have to be documented when the C texi2any possibility is documented. > I don't see the need of an --no-embed-interpreter option, and if this > was an option it could be a source of incompatibility with it working > differently across Texinfo releases. Now there is only one ctexi2any specific command-line option that remains, --mimick, which is used to set the program name to texi2any instead of using argv[0] basename (which would be ctexi2any). This may not be needed if the program is compiled as/installed as texi2any. -- Pat
