On Wed, Oct 25, 2023 at 10:12:48PM +0100, Gavin Smith wrote:
> On Tue, Oct 24, 2023 at 06:15:06PM +0200, Patrice Dumas wrote:
> There still seems to be lacking any way to turn off the new XS code that
> is being run, in order to judge the performance impact. TEXINFO_XS_PARSER
> is now used for a l
On Wed, Oct 25, 2023 at 07:41:09PM +0300, Eli Zaretskii wrote:
> The warning is real: wchar_t is a 16-bit data type on MS-Windows,
> whereas the code assumes it's of the same width as wint_t.
>
> I changed the offending code to say this instead:
>
> if (!strchr (end_sentence_charact
On Tue, Oct 24, 2023 at 06:15:06PM +0200, Patrice Dumas wrote:
> Maybe it is because of the C code that is run in parallel with perl code?
> That would be my first guess. Hopefully, the default will be not to run
> C and perl in parallel for the release. Maybe you could compare with
> a run with
t/test_tree_copy.t, which is run as part of the test suite, prints an
error:
$ perl -w t/test_tree_copy.t
1..7
ok 1 - modules loading
ERROR: copy_tree: no tree_document_descriptor
ok 2 # skip test perl not XS
ok 3 - tree to texi and original match
ok 4 - tree and copy to texi match
ok 5 - tree aft
One thing I've been thinking of doing for a while is to make Texinfo
programs meet the XDG standard:
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
The only file I'm aware of is .infokey for the info program, but there
may be others. This would mean that the file mo
> From: Gavin Smith
> Date: Mon, 23 Oct 2023 19:52:49 +0100
> Cc: bug-texinfo@gnu.org
>
> I propose the following, more finished patch, which applies
> to Texinfo 7.1. We can also do something similar for the master branch.
Unfortunately, this change doesn't work on MS-Windows:
libtool: comp
