On Wed, Apr 10, 2024 at 09:57:19PM +0200, Patrice Dumas wrote:
> Hello,
>
> With CHECK_NORMAL_MENU_STRUCTURE set to 1, there is a warning by
> texi2any:
>
> a.texi:10: warning: node `node after chap1' is next for `chap1' in menu but
> not in sectioning
>
> for the following code:
>
> @node
On Fri, Apr 05, 2024 at 11:02:14PM +0200, Patrice Dumas wrote:
> > I've committed a change to remove the $no_build parameter but not the
> > $no_store parameter.
>
> It seems to me that the changes are no complete, to me the _get_parser_info
> $no_build argument should be removed too, and the
On Fri, Apr 05, 2024 at 12:20:19AM +0200, Patrice Dumas wrote:
> I do not think that having the same interface for XS and pure Perl is
> important. It could even make clearer what is going on in XS. What is
> important is to have a code that is easy to understand as a whole in my
> opinion.
>
>
On Wed, Apr 03, 2024 at 11:53:09PM +0200, Patrice Dumas wrote:
> To avoid that, you could change the special call to $document->tree
> with an argument, like $document->tree(1) to be $document->tree(), as
> the argument, which is only taken in into account in XS is such that an
> handler only is
On Wed, Apr 03, 2024 at 11:53:09PM +0200, Patrice Dumas wrote:
> On Wed, Apr 03, 2024 at 09:23:28PM +0100, Gavin Smith wrote:
> > This does appear to make texi2any work with TEXINFO_XS_STRUCTURE=0, although
> > there are various test failures that I haven't investigated properly
On Wed, Apr 03, 2024 at 09:23:29PM +0100, Gavin Smith wrote:
> We previously discussed the interface of the XS modules and trying to
> improve their abstraction so that the same interface was used for both
> XS and non-XS code. (Emails from 2024-02-23 "Better abstraction of
>
We previously discussed the interface of the XS modules and trying to
improve their abstraction so that the same interface was used for both
XS and non-XS code. (Emails from 2024-02-23 "Better abstraction of
Texinfo::Document interface regardless of XS".) We made changes in
this direction.
On Wed, Apr 03, 2024 at 02:21:22PM +0200, Patrice Dumas wrote:
> Hello,
>
> I propose to rename BODYTEXT as BODY_ELEMENT_ATTRIBUTES, I find BODYTEXT
> not specific enough and confusing. It would also be more consistent
> with the HTML_ROOT_ELEMENT_ATTRIBUTES customization variable name, which
>
On Wed, Apr 03, 2024 at 05:09:28PM +0200, Patrice Dumas wrote:
> Hello,
>
> I would like to remove two customization options:
>
> NO_USE_SETFILENAME
> If set, do not use @setfilename to set the document name; instead, base the
> output document name only on the input file name. The default is
On Sun, Mar 31, 2024 at 10:58:08PM +0200, Patrice Dumas wrote:
> Hello,
>
> If the customization variable COMPLEX_FORMAT_IN_TABLE is set,
> @indentedblock and indented fixed-width font @-commands, @example,
> @display and @lisp are indented with a table (instead of using ).
>
> I think that the
On Wed, Apr 03, 2024 at 12:09:04PM +0200, Patrice Dumas wrote:
> On Tue, Apr 02, 2024 at 09:56:40PM +0100, Gavin Smith wrote:
> > If a cross-reference appears like
> >
> > @xref{,,, texi2any_api, GNU Texinfo @command{texi2any} Output
> > Customization}.
>
If a cross-reference appears like
@xref{,,, texi2any_api, GNU Texinfo @command{texi2any} Output Customization}.
with no first argument, then this is output in Info like
*Note (texi2any_api)::.
- with no node argument following the manual. The Info browser (at least
recent versions of it; I
On Sun, Mar 31, 2024 at 10:13:03PM +0200, Patrice Dumas wrote:
> Hello,
>
> I propose to remove the HTML customization variable
> AVOID_MENU_REDUNDANCY:
>
> If set, and the menu entry and menu description are the
> same, then do not print the menu description; default false.
>
> It seems to
On Sat, Mar 16, 2024 at 03:53:45PM +0100, Patrice Dumas wrote:
> Hello,
>
> In a recent thread, on help-texinfo, Eli raised valid concerns on the
> documentation of customization variables of texi2any, see for example:
> https://lists.gnu.org/archive/html/help-texinfo/2024-03/msg00014.html
On Thu, Mar 14, 2024 at 11:36:49PM +0100, Patrice Dumas wrote:
> > I didn't really know what this part meant:
> >
> > Index entries and comments that are given before an @code{@@item}
> > including the first, are automatically moved (internally) to after the
> > @code{@@item}, so the
On Thu, Mar 14, 2024 at 11:36:49PM +0100, Patrice Dumas wrote:
> On Tue, Mar 12, 2024 at 06:39:46PM +0000, Gavin Smith wrote:
> > I think both should be documented as being valid. I don't mind which one
> > is presented as more normal. I have edited the node in the documentati
On Wed, Mar 13, 2024 at 03:42:19PM -0700, Raymond Toy wrote:
> > I think both should be documented as being valid. I don't mind which one
> > is presented as more normal. I have edited the node in the documentation
> > slightly.
> >
> > It would be ok to change the example to show "@itemize
On Thu, Mar 07, 2024 at 09:49:24AM +0100, Patrice Dumas wrote:
> On Wed, Mar 06, 2024 at 09:54:18PM +0100, Bruno Haible wrote:
> > Gavin Smith wrote:
> > > it is not worth changing and making practically every use of
> > > @itemize in a Texinfo manual being flagged
On Tue, Mar 05, 2024 at 10:45:54PM +0100, Patrice Dumas wrote:
> On Tue, Mar 05, 2024 at 07:44:33PM +0000, Gavin Smith wrote:
> > I don't agree with changing the language to require braces. There is
> > not a good reason to change it. Although writing "@itemize @bullet{}"
On Wed, Mar 06, 2024 at 03:05:06PM +0100, pertu...@free.fr wrote:
> > I suggest
> >
> > ```
> > '@asis' needs braces here; say '@itemize @asis{}'.
> > ```
>
> I do not like much that option, because we do not have any idea why the
> user ended up using '@itemize @asis'. Maybe with @asis, it
On Tue, Mar 05, 2024 at 11:59:23AM +0100, Patrice Dumas wrote:
> On Mon, Mar 04, 2024 at 09:16:44PM +0000, Gavin Smith wrote:
> > \itemcontents expands to \asis and then TeX tries to take the } following
> > as the argument to \asis, which is invalid.
> >
> > Basica
On Mon, Mar 04, 2024 at 03:59:26PM +0100, Bruno Haible wrote:
> @itemize @asis
> seems to work in HTML and info mode only, not in TeX mode.
>
>
> How to reproduce (with texinfo-7.1):
Patrice covered most of it.
It reproduces with any test file with "@itemize @asis" in it.
>
On Tue, Feb 27, 2024 at 10:38:37PM +0100, Patrice Dumas wrote:
> On Tue, Feb 27, 2024 at 08:10:31PM +0000, Gavin Smith wrote:
> > On Mon, Feb 26, 2024 at 01:15:47AM +0100, Patrice Dumas wrote:
> > > I did wrappers wrappers around functions to avoid mixing Perl and non-Perl
>
On Mon, Feb 26, 2024 at 01:15:47AM +0100, Patrice Dumas wrote:
> On Fri, Feb 23, 2024 at 07:27:55PM +0000, Gavin Smith wrote:
> > It is bad at any time. I'm not sure what situation you refer to by "link
> > time". As far as I understand, the Perl headers redefine (or can
On Sun, Feb 25, 2024 at 09:00:55PM +0100, Patrice Dumas wrote:
> On Sun, Feb 25, 2024 at 07:43:42PM +0000, Gavin Smith wrote:
> > It appears that there was no effort made to reset the counters at all.
> > If a parser run finished with one of the counters active, it would
&g
On Sun, Feb 25, 2024 at 07:01:22PM +, Gavin Smith wrote:
> So it appears there is a problem with the counter not being reset properly
> before the test runs, or sometime early on in the run.
>
> I'll try and do more investigation.
It appears that there was no effort m
On Sun, Feb 25, 2024 at 04:47:46PM +, Gavin Smith wrote:
> I occasionally get test failures in the
> "perl -w t/03coverage_braces.t definfoenclose_texinfo_commands" test,
> but cannot usually repeat it reliably. I suspect some issue with memory
> corruption or issue wit
I occasionally get test failures in the
"perl -w t/03coverage_braces.t definfoenclose_texinfo_commands" test,
but cannot usually repeat it reliably. I suspect some issue with memory
corruption or issue with uninitialised memory, although I've not managed
to get anything to show up with valgrind
On Fri, Feb 23, 2024 at 05:33:53PM +0100, Patrice Dumas wrote:
> Hello,
>
> There are notes in C code warning against calling malloc or free and
> functions potentially redefined by gnulib in files which include the
> perl headers. It may be related to the discussion here:
>
>
On Mon, Nov 06, 2023 at 07:52:40PM +0100, Andreas Schwab wrote:
> On Nov 06 2023, Gavin Smith wrote:
>
> > $ readelf -d /usr/local/lib/texinfo/ConvertXS.so | grep RUNPATH
> > 0x001d (RUNPATH)Library runpath:
> > [/usr/local/lib/texinfo
On Sun, Feb 18, 2024 at 10:57:22PM +0100, Patrice Dumas wrote:
> On Sun, Feb 18, 2024 at 06:09:23PM +0000, Gavin Smith wrote:
> > If this is ok, then "convert" could set $self->{'encoding_disabled'}.
>
> Should I do that part?
I tried making the change myself.
On Sun, Feb 18, 2024 at 01:27:12PM +0100, Roland Clobus wrote:
> Hello texinfo maintainers,
>
> While working on reproducible live images [1], I noticed that the sort order
> in the file /usr/share/info/dir is unstable when nearly identical entries
> are added.
>
> The order of the pairs 'diff',
On Sun, Feb 18, 2024 at 02:13:13PM +0100, Patrice Dumas wrote:
> Hello,
>
> This is in the new encode once only stream code, so I ask here before
> making a change, I could be missing something, Gavin you probably
> will have comments/advices.
>
> I do not think that it is a good thing to set
On Tue, Feb 13, 2024 at 05:37:03PM +0100, Patrice Dumas wrote:
> On Mon, Feb 05, 2024 at 06:14:16PM +0000, Gavin Smith wrote:
> > On Sun, Feb 04, 2024 at 10:27:00PM +0100, Patrice Dumas wrote:
> > > removed at any time. Also calling it something else, like
> > >
On Fri, Feb 09, 2024 at 04:56:36PM +, Francesco Turco wrote:
> Hello.
>
> I have GNU texinfo 7.1 on a Gentoo Linux system.
>
> I can make texinfo reliably crash with the following simple steps:
> 1. M-x set-variable
> 2. Type "link-style" (without quotes)
> 3. Type "foo" (without quotes)
>
On Sun, Feb 04, 2024 at 04:18:27PM +, Werner LEMBERG wrote:
> Indeed, because it is not too an exotic feature. In LilyPond, we have
> a bunch of smaller files that get included in a master document; every
> file comprises a section of the document and essentially starts with
>
> ```
>
On Tue, Feb 06, 2024 at 07:13:09PM +0100, Patrice Dumas wrote:
> On Mon, Feb 05, 2024 at 07:35:59PM +0000, Gavin Smith wrote:
> > I don't know if uniconv/u8-conv-from-enc is a necessary module. It's
> > not easy to find out how the module is used as the documentation
On Sun, Feb 04, 2024 at 07:59:37PM +, Gavin Smith wrote:
> I can't build from commit 5154587461e (2024-02-04). It ends with the
> errors:
>
> make[2]: Entering directory '/home/g/src/texinfo/GIT/tp/Texinfo/XS/gnulib/lib'
> gperf -m 10 ./iconv_open-aix.gperf > ./iconv_open
On Sun, Feb 04, 2024 at 10:27:00PM +0100, Patrice Dumas wrote:
> > > However, if there is a
> > > possibility to get variable elements set to "non-ignorable" in C,
> > > possibly by using an hardcoded locale of en_US, it will not possible to
> > > get automatically both the correct and more rapid
On Sun, Feb 04, 2024 at 08:38:45PM +0100, Patrice Dumas wrote:
> Thanks. This is very confusing to me, then, as it is not told that way
> in perllocale, especially the section:
> https://perldoc.perl.org/perllocale#Category-LC_COLLATE%3A-Collation%3A-Text-Comparisons-and-Sorting
> There is more
On Sun, Feb 04, 2024 at 08:38:45PM +0100, Patrice Dumas wrote:
> >offer much more powerful solutions to collation issues.
> >
> > - from "man perlop".)
>
> Thanks. This is very confusing to me, then, as it is not told that way
> in perllocale, especially the section:
>
I can't build from commit 5154587461e (2024-02-04). It ends with the
errors:
make[2]: Entering directory '/home/g/src/texinfo/GIT/tp/Texinfo/XS/gnulib/lib'
gperf -m 10 ./iconv_open-aix.gperf > ./iconv_open-aix.h-t && \
mv ./iconv_open-aix.h-t ./iconv_open-aix.h
/bin/bash: line 1: gperf: command
On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > An alternative is not to have such a variable but just to have an option
> > to collate according to the user's locale. Then the user would run e.g.
> > "LC_COLLATE=ll_LL.UTF-8 texi2any ..." to use collation from the ll_LL.UTF-8
>
On Sun, Feb 04, 2024 at 12:17:16PM +0100, Patrice Dumas wrote:
> On Thu, Feb 01, 2024 at 10:16:07PM +0000, Gavin Smith wrote:
> > An alternative is not to have such a variable but just to have an option
> > to collate according to the user's locale. Then the user would run e.g.
On Thu, Feb 01, 2024 at 12:37:29PM +, Werner LEMBERG wrote:
>
> In the texinfo manual of version 7.1 I can find the following about
> `@unmacro`:
>
>
>You can undefine a macro FOO with ‘@unmacro FOO’. It is not an
>error to undefine a macro that is already undefined. For example:
On Thu, Feb 01, 2024 at 09:01:42AM +0200, Eli Zaretskii wrote:
> > Date: Wed, 31 Jan 2024 23:11:02 +0100
> > From: Patrice Dumas
> >
> > > Moreover, en_US.utf-8 will use collation appropriate for (US) English.
> > > There may be language-specific "tailoring" for other languages (e.g.
> > >
On Wed, Jan 31, 2024 at 10:38:36AM +0100, Patrice Dumas wrote:
> With collation also possible with XS/C, but with a different result than
> in perl, I think that there should be a way to use perl unicode
> collation from C too, in addition to using a unicode collation or not.
>
> Should it be a
On Wed, Jan 31, 2024 at 10:15:08AM +0100, Patrice Dumas wrote:
> Hello,
>
> I implemented index sorting in C with XS interface in texi2any.
> When unicode collation is wanted, based on my understanding of
> Eli suggestions, a collation locale is set to "en_US.utf-8", by
> newlocale
On Tue, Jan 30, 2024 at 10:34:43PM -0500, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> When I
On Mon, Jan 29, 2024 at 01:10:52AM +, Erik A Johnson wrote:
> Without libintl.h, tp/Texinfo/XS/parsetexi/api.c does not compile -- even
> though configure tests for libintl.h. In api.c, is the line
>
> #include
>
> actually needed? (Commenting that line out in texinfo-7.1 allows it
On Sun, Jan 28, 2024 at 09:25:38PM +0100, Patrice Dumas wrote:
> On Sun, Jan 28, 2024 at 08:15:33PM +0000, Gavin Smith wrote:
> > Below is a patch to introduce a new variable to avoid using the
> > Unicode::Collate module. Turning the module off shortens run times by
> >
On Sun, Jan 28, 2024 at 09:13:21PM +0100, Patrice Dumas wrote:
> On Sat, Jan 27, 2024 at 05:55:24PM +0000, Gavin Smith wrote:
> > The get_constant function has been recently added but I think the name of
> > this is too generic.
>
> Any idea on another name?
It reminds me
Below is a patch to introduce a new variable to avoid using the
Unicode::Collate module. Turning the module off shortens run times by
about 5% (depending on the size of indices in the document).
Users can use this if they don't find texi2any fast enough, if they
don't care about having the
On Sat, Jan 27, 2024 at 06:47:24PM +, Gavin Smith wrote:
> On Sat, Jan 27, 2024 at 07:20:05PM +0100, Patrice Dumas wrote:
> > > I don't know how ffmpeg or other packages are supposed to adapt to the
> > > new interface. Perhaps we could put special case code in ge
On Sat, Jan 27, 2024 at 07:20:05PM +0100, Patrice Dumas wrote:
> > I don't know how ffmpeg or other packages are supposed to adapt to the
> > new interface. Perhaps we could put special case code in get_conf to
> > check for "PACKAGE_VERSION" and redirect to the new interface?
>
> That seems
On Sat, Jan 27, 2024 at 04:26:10PM +0100, Patrice Dumas wrote:
> Hello,
>
> On Sun, Nov 05, 2023 at 12:13:00PM +0100, Arsen Arsenović wrote:
> >
> > Patrice Dumas writes:
> >
> > > my $texinfo_version = texinfo_get_conf('PACKAGE_VERSION');
> > > $texinfo_version =~ s/\+dev$//;
> > > #
On Fri, Jan 26, 2024 at 03:57:24PM +0100, Patrice Dumas wrote:
> Hello,
>
> With an objective to improve gendoc.sh texinfo sources tarball
> generation code, I implemented, in the developpement version in git
> the possibility with texi2any to output the @include files included
> from a manual,
On Mon, Jan 22, 2024 at 10:50:07PM +0100, pertu...@free.fr wrote:
> On Sun, Jan 21, 2024 at 03:13:25PM -0700, Karl Berry wrote:
> > Hi Patrice,
> >
> > I understand the principle, but for me the lossage in practice is even
> > more unfortunate (by far). It sure seems to me that the "rare" case
>
On Sat, Jan 20, 2024 at 06:45:06PM +0100, Patrice Dumas wrote:
> > That reply pertained to the case of a missing menu entry. Your case
> > is the opposite: a superfluous menu entry.
>
> To me, the manual with an entry leading to a node that do not
> corresponds to the sectioning structure is
On Thu, Jan 18, 2024 at 04:57:15PM -0700, Karl Berry wrote:
> I believe this is an intentional feature in recent Texinfo versions.
> To get the warnings back, you need to run makeinfo with the
> command-line option "-c CHECK_NORMAL_MENU_STRUCTURE=1".
>
> Thanks for the hint. I
On Tue, Jan 16, 2024 at 08:50:29AM +, Bugsy Abatantuono wrote:
> With `hide-note-references=On` (“hide some Info file syntax in the text
> of nodes”) it’s more readable; namely, “see X” reads better than
> `*note X::`. However, with that, `find-menu` will always report “No
> menu in this
On Tue, Jan 16, 2024 at 08:30:14AM +, Bugsy Abatantuono wrote:
> Steps to reproduce bug:
>
> 1. Content of the file ./keys:
>
> #info
> a invalid
>
> 2. Run: info —init-file ./keys
> 3. Type: H (segfault)
>
> --version: info (GNU texinfo) 7.0.2
>
Thanks for the report; it should
On Tue, Jan 16, 2024 at 08:32:37AM +, Bugsy Abatantuono wrote:
> Steps to reproduce bug:
>
> 1. Run: info —init-file /dev/null '(info-stnd)Xref Commands'
> 2. Type: M-x visit-menu
> 3. Type: x (segfault)
>
> --version: info (GNU texinfo) 7.0.2
>
Thanks for the report. It should be fixed
On Wed, Jan 03, 2024 at 04:17:02AM +, D Chate wrote:
> Hi
>
> Sorry to even mention: the 2nd link near the end of
> this page:
> https://www.gnu.org/software/texinfo
> currently reads:
> "Info brower introduction"
> not:
> "Info browser introduction"
>
Thanks for reporting it, it's no
On Tue, Dec 26, 2023 at 08:17:32PM -0500, Mike Frysinger wrote:
> There are other http:// URIs that could be updated, but I wanted to focus
> on the texinfo homepage to start with. I also left the DTD URI alone as
> those act more as permanent unique ids rather than exact URIs that people
>
On Fri, Dec 22, 2023 at 03:49:26PM -0300, Rammon Resende wrote:
> INFO command in linux ubuntu is installed and is giving the following
> error in the terminal: aborted (core image saved)
>
> I try to use the command but it always shows this error, I have already
> reinstalled and installed it
On Wed, Dec 13, 2023 at 01:41:01PM +0200, Eli Zaretskii wrote:
> > We'll probably have to investigate each of these changes separately to
> > see where they occur. I am probably not going to fix them all in one
> > go.
> >
> > First, could you confirm which version of Texinfo you got these
On Sat, Oct 14, 2023 at 09:41:46AM +0300, Eli Zaretskii wrote:
> > Eli, are you able to test this from git or do you need me to make another
> > pretest release?
>
> Git is a bit problematic, as some of the file names include non-ASCII
> characters. For this reason, and also for others (e.g., I
On Tue, Dec 12, 2023 at 08:21:29PM +, Gavin Smith wrote:
> > modified: tp/Texinfo/XS/TestXS.c
>
> This file was modified. It is probably because xsubpp ran to regenerate
> TestXS.c.
>
> This issue was previously reported:
>
> https://lists.gnu.org/archi
On Tue, Dec 12, 2023 at 08:21:29PM +, Gavin Smith wrote:
> > modified: po_document/ca.po
>
> Likewise. po files being updated is a perennial nuisance that I thought
> we had got right with documenting release procedures exactly, but evidently
> it still isn't
On Wed, Dec 13, 2023 at 09:31:16AM +0100, Patrice Dumas wrote:
> On Tue, Dec 12, 2023 at 09:01:30PM +0000, Gavin Smith wrote:
> > I cannot currently build from master. It gets this far:
>
> There was a missing dTHX. Here is a patch:
> https://git.savannah.gnu.org/cgit/texi
I cannot currently build from master. It gets this far:
libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I./main
-I./structuring_transfo -I./convert -I. -DDATADIR=\"/usr/local/share\"
-I./gnulib/lib -I./gnulib/lib -DVERSION=\"0\" -DXS_VERSION=\"0\"
On Sun, Dec 10, 2023 at 04:00:56PM +0100, Preuße, Hilmar wrote:
> Hello,
>
> I got a report telling that "make distclean" does not bring back the build
> tree into the original state. After running a build (configure line below)
> and calling "make distclean", we have a few differences. Some
On Sat, Dec 02, 2023 at 01:28:49PM -0700, arn...@skeeve.com wrote:
> Hi.
>
> Thanks for the response. I do have a number of floats (it's a good-
> sized book) but this may be the only table that is so large.
> It is important that I refer to the floats from the text with an xref.
>
> Since the
On Thu, Nov 30, 2023 at 05:03:21PM -0600, axelbo...@yahoo.com wrote:
> Hello,
>
>
>
> please consider adding emacs info-mode to the list of info readers at
> https://www.gnu.org/software/texinfo/links.html.
>
Emacs Info mode was the main reason for the sentence, "The Texinfo system
is
On Fri, Dec 01, 2023 at 10:45:14AM +0200, Aharon Robbins wrote:
> Hi.
>
> Using version 2023-10-19.19 of texinfo.tex, there is a problem if
> a table inside @float goes over one page. See the attached file.
>
> If the table is not inside @float, it formats just fine across
> multiple pages.
On Sat, Nov 25, 2023 at 09:35:28AM +0100, Patrice Dumas wrote:
> > It seems that we could stop these structures being modified with the
> > addition of a flag on the parser (e.g. $parser->{'locked'} or
> > $parser->{'simple'}). Then check this flag any time:
> >
> > * A new Texinfo command is to
/translate_txiinternalvalue_macro.init
delete mode 100644
tp/t/results/init_files_tests/macro_defined_txiinternalvalue_in_translation.pl
diff --git a/ChangeLog b/ChangeLog
index fec8ab7980..0c336d739c 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,13 @@
+2023-11-25 Gavin Smith
+
+ * tp/Texinfo
| 2 +-
.../res_html/index.html | 8 ++--
5 files changed, 26 insertions(+), 46 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index b50d9056e8..fec8ab7980 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,17 @@
+2023-11-25 Gavin Smith
+
+ Parser
insertions(+), 26 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 318e84f2e5..b50d9056e8 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,16 @@
+2023-11-25 Gavin Smith
+
+ Re-add simple_parser
+
+ * tp/Texinfo/ParserNonXS.pm, tp/Texinfo/XS/parsetexi/Parsetexi.pm
+ (parser
On Sat, Nov 25, 2023 at 09:35:28AM +0100, Patrice Dumas wrote:
> On Fri, Nov 24, 2023 at 11:24:55PM +0000, Gavin Smith wrote:
> > As I understand it, it is not any part of the state that is problematic
> > to modify for simple_parser. It is only the structures that are refer
On Sun, Nov 05, 2023 at 12:53:19PM +0100, Patrice Dumas wrote:
> Indeed, I don't know why I want it to have an effect, as it should
> not...
>
> > If there is a real problem, then we could fix it another way, maybe
> > by "locking" the parser configuration at certain points, making any
> >
On Fri, Nov 24, 2023 at 10:07:30PM +0100, Patrice Dumas wrote:
> Hello,
>
> The extra_integer associated type is used for extra information in
> Texinfo tree elements in C that correspond to integers. Currently the
> associated type is long, but in most cases, it is used as an int. I
> think
On Tue, Nov 14, 2023 at 08:40:54AM +0100, Patrice Dumas wrote:
> The other is that PERL_CONF_optimize is used for AM_CFLAGS
> (XSLIBS_CFLAGS in the development version), the objective being that the
> same flags as those used to build perl are used for perl XS modules. I
> guess that these flags
On Tue, Nov 14, 2023 at 02:22:00PM +0200, Eli Zaretskii wrote:
> AFAIU, that's impossible in general, because CFLAGS could include
> flags that cannot be applied to both CC and PERL_CONF_cc due to
> compatibility issues, since Perl could have been built using a very
> different compiler.
>
>
On Thu, Sep 21, 2023 at 06:06:34PM +0200, Patrice Dumas wrote:
> On Wed, Sep 20, 2023 at 08:44:34PM +0100, Gavin Smith wrote:
> > One change at a time please. Any gnulib tests should be run
> > with the same compiler flags as used to compile the shared library.
>
On Wed, Nov 15, 2023 at 09:42:21AM +0100, Patrice Dumas wrote:
> On Wed, Nov 15, 2023 at 12:22:24AM -0800, Paul Eggert wrote:
> > On 2023-11-13 01:28, Patrice Dumas wrote:
> > > According to your mail
> > > https://lists.gnu.org/archive/html/bug-libunistring/2023-11/msg0.html
> > >
> > >
valgrind was reporting a memory leak in texi2any, like:
==3404772== 364 bytes in 1 blocks are definitely lost in loss record 128 of 151
==3404772==at 0x4848899: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==3404772==by 0x498D11F: newlocale (newlocale.c:199)
On Tue, Nov 14, 2023 at 10:16:33PM +0100, Bruno Haible wrote:
> Sam James wrote:
> > > It appears that the obstack gnulib module is the culprit.
>
> I replied:
> > Therefore, if it is a bug in gnulib, it is also a bug in glibc.
>
> Sam was right. I was wrong. It is a bug in the 'obstack' gnulib
On Sun, Nov 12, 2023 at 12:41:58PM +0100, John Paul Adrian Glaubitz wrote:
> > diff tree.c.old tree.c -u
> > --- tree.c.old 2023-11-04 16:15:13.632755680 +
> > +++ tree.c 2023-11-04 16:16:36.211072521 +
> > @@ -43,7 +43,10 @@
> >if (obs_element_first)
> > obstack_free
On Mon, Nov 13, 2023 at 10:28:35AM +0100, Patrice Dumas wrote:
> According to your mail
> https://lists.gnu.org/archive/html/bug-libunistring/2023-11/msg0.html
>
> char32_t is less portable, and indeed, the solaris automatic build sees
> to fail because of char32_t is not available, while
On Sat, Nov 11, 2023 at 11:54:52PM +0100, Bruno Haible wrote:
> [CCing bug-libunistring]
> Gavin Smith wrote:
> > I did not understand why uc_width was said to be "locale dependent":
> >
> > "These functions are locale dependent."
> >
> >
On Sun, Nov 05, 2023 at 12:13:00PM +0100, Arsen Arsenović wrote:
> Oh, interesting. On my system, I'm using texinfo built from master, and
> it completely lacks PACKAGE_VERSION! (if I rebuild from releases/7.1,
> it's present). It looks like it got removed in
>
On Sat, Nov 11, 2023 at 09:06:41PM +0100, Bruno Haible wrote:
> [CCing bug-gnulib]
> Indeed, the c32* functions by design work only on those Unicode characters
> that can be represented as multibyte sequences in the current locale.
>
> I'll document this better in the Gnulib manual.
>
> Since
On Fri, Nov 10, 2023 at 07:39:43PM +, Gavin Smith wrote:
> Is the expected output
>
>å å (å) Å Å (Å) æ æ (æ) œ œ (œ) Æ Æ (Æ) Œ Œ (Œ) ø ø (ø) Ø Ø (Ø) ß ß (ß)
>
> (width 74) or
>
>@aa å (å) @AA Å (Å) @ae æ (æ) @oe œ (œ) @AE Æ (Æ) @OE Œ (Œ) @o ø (ø) @O Ø
> (Ø)
On Fri, Nov 10, 2023 at 08:47:10AM +0200, Eli Zaretskii wrote:
> > Does anybody know if we could just write 'a' instead of U'a' and rely
> > on it being converted?
> >
> > E.g. if you do
> >
> > char32_t c = 'a';
> >
> > then afterwards, c should be equal to 97 (ASCII value of 'a').
>
> Why
Forwarding reply from Bruno as I accidentally dropped the list when
replying.
- Forwarded message from Bruno Haible -
Date: Fri, 10 Nov 2023 03:27:14 +0100
From: Bruno Haible
To: Gavin Smith
Subject: Re: Locale-independent paragraph formatting [was Re: Texinfo 7.0.93
pretest
On Thu, Nov 09, 2023 at 04:12:21PM -0500, Jonathan Dushoff wrote:
> Thanks for responding!
>
> etex, pdftex and pdflatex all seem to take the jobname argument, which
> may be what's wanted. Alternatively, you could consider mentioning
> briefly in the documentation that -o simply moves the output
(Reply accidentally not sent to the list.)
- Forwarded message from Gavin Smith -
Date: Thu, 9 Nov 2023 21:25:28 +
From: Gavin Smith
To: Bruno Haible
Subject: Re: Locale-independent paragraph formatting [was Re: Texinfo 7.0.93
pretest available]
On Thu, Nov 09, 2023 at 08
(Reply accidentally not sent to list.)
- Forwarded message from Gavin Smith -
Date: Thu, 9 Nov 2023 20:11:59 +
From: Gavin Smith
To: Bruno Haible
Subject: Locale-independent paragraph formatting [was Re: Texinfo 7.0.93
pretest available]
On Tue, Oct 10, 2023 at 07:29:15PM
1 - 100 of 2302 matches
Mail list logo
