Re: HTML customization files and command-line options processing order

2025-01-19 Thread Gavin Smith
On Sat, Jan 18, 2025 at 10:27:08AM +0100, Patrice Dumas wrote: > 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

Re: HTML customization files and command-line options processing order

2025-01-18 Thread Patrice Dumas
On Sun, Jan 12, 2025 at 08:28:26PM +, 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

Re: HTML customization files and command-line options processing order

2025-01-13 Thread Gavin Smith
On Sun, Jan 12, 2025 at 10:49:01PM +0100, Patrice Dumas wrote: > > 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. > > I do not get the point here. A good reaso

Re: HTML customization files and command-line options processing order

2025-01-12 Thread Patrice Dumas
On Sun, Jan 12, 2025 at 08:28:26PM +, Gavin Smith wrote: > On Tue, Jan 07, 2025 at 10:30:22PM +0100, Patrice Dumas wrote: > > This is only one of the possibility, another possibility could be to > > have --no-embed-interpreter ignored if an init file has already been > > loaded and the embedded

Re: HTML customization files and command-line options processing order

2025-01-12 Thread Gavin Smith
On Tue, Jan 07, 2025 at 10:30:22PM +0100, Patrice Dumas wrote: > This is only one of the possibility, another possibility could be to > have --no-embed-interpreter ignored if an init file has already been > loaded and the embedded interpreter is started and to have init files > loading override the