Re: Use of `@pxref`

> From: Gavin Smith > Date: Fri, 1 Aug 2025 23:09:10 +0100 > Cc: bug-texinfo@gnu.org > > The last sentence here was an attempt to work around the limitations of > Info format. @pxref{foo} and @ref{foo} have identical output in Info > ("*note foo::"), but in other output formats, @pxref{foo} gene

Re: Use of `@pxref`

>> What am I missing? >> > > The last sentence here was an attempt to work around the limitations > of Info format. @pxref{foo} and @ref{foo} have identical output in > Info ("*note foo::"), but in other output formats, @pxref{foo} > generates "see foo" and @ref generates "foo". Some attempt is

Re: Use of `@pxref`

On Fri, Aug 01, 2025 at 03:30:29AM +, Werner LEMBERG wrote: > > In the section documenting `@pxref` there is the following paragraph. > >In past versions of Texinfo, it was not allowed to write >punctuation after a ‘@pxref’, so it could be used _only_ before a >right parenthesis.

Re: comma-separated footnote numbers

>> I have no idea whether this is possible to implement with the >> current footnote mechanism in `texinfo.tex` :-) > > It's fairly easy with the right trick ;-) We can add a small penalty > after each footnote and then use \lastpenalty to check if we are > immediately after another footnote, an

Re: comma-separated footnote numbers

On Thu, Jul 31, 2025 at 08:20:39PM +0100, Gavin Smith wrote: > On Thu, Jul 31, 2025 at 08:08:06PM +0100, Gavin Smith wrote: > > I had issues with the spacing around the commas, as there was too much > > space before the commas. (In fact, the examples at that stackexchange > > didn't look quite rig

Re: comma-separated footnote numbers

On Thu, Jul 31, 2025 at 08:08:06PM +0100, Gavin Smith wrote: > I had issues with the spacing around the commas, as there was too much > space before the commas. (In fact, the examples at that stackexchange > didn't look quite right, either.) I got a better result by setting > \scriptsize to 0pt f

Re: comma-separated footnote numbers

On Thu, Jul 31, 2025 at 06:14:58AM +, Werner LEMBERG wrote: > > [texinfo.tex 2025-07-15.21] > > > Consider this input file > > ``` > \input texinfo > > This is a text@footnote{Foo.}@footnote{Bar.}@footnote{Baz.} with some > footnotes in succession. > > @bye > ``` > > As can be seen in th

Re: help for the Perl swig interface tests failing on cygwin in CI

On Wed, Jul 30, 2025 at 02:30:44PM +0300, Eli Zaretskii wrote: > > Date: Tue, 29 Jul 2025 18:53:41 +0200 > > From: Patrice Dumas > > Cc: bug-texinfo@gnu.org > > > > On Tue, Jul 29, 2025 at 07:04:27PM +0300, Eli Zaretskii wrote: > > > It's very simple: you need to make sure the directory where the

Re: help for the Perl swig interface tests failing on cygwin in CI

> Date: Tue, 29 Jul 2025 18:53:41 +0200 > From: Patrice Dumas > Cc: bug-texinfo@gnu.org > > On Tue, Jul 29, 2025 at 07:04:27PM +0300, Eli Zaretskii wrote: > > It's very simple: you need to make sure the directory where the DLL > > lives is on PATH or in the same directory from where you invoke th

Re: help for the Perl swig interface tests failing on cygwin in CI

Hi Patrice, Patrice Dumas writes: > There is a new SWIG interface in Texinfo, in tta/swig, and some tests > for the Perl interface in tta/swig/perl. In the CI > https://github.com/gnu-texinfo/ci-check/actions/runs/16592419646/job/46931708709 > the tta/swig/perl tests fail for cygwin with the SW

Re: help for the Perl swig interface tests failing on cygwin in CI

On Tue, Jul 29, 2025 at 07:04:27PM +0300, Eli Zaretskii wrote: > > Date: Tue, 29 Jul 2025 14:53:19 +0200 > > From: Patrice Dumas > > > > Hello, > > > > There is a new SWIG interface in Texinfo, in tta/swig, and some tests > > for the Perl interface in tta/swig/perl. In the CI > > https://github

Re: help for the Perl swig interface tests failing on cygwin in CI

> Date: Tue, 29 Jul 2025 14:53:19 +0200 > From: Patrice Dumas > > Hello, > > There is a new SWIG interface in Texinfo, in tta/swig, and some tests > for the Perl interface in tta/swig/perl. In the CI > https://github.com/gnu-texinfo/ci-check/actions/runs/16592419646/job/46931708709 > the tta/sw

Re: portability and use of WEXITSTATUS

On Tue, Jul 29, 2025 at 01:00:58PM +0200, Patrice Dumas wrote: > Hello, > > The CI at github for the mingw on cygwin leads to failing link of info > with: > /usr/lib/gcc/i686-w64-mingw32/13/../../../../i686-w64-mingw32/bin/ld: > run-external.o: in function `get_output_from_program': > /cygdrive/d

Re: info.js demo on Texinfo manual updated on website

Link to archived email: https://lists.gnu.org/archive/html/bug-texinfo/2022-11/msg00239.html On Wed, Nov 30, 2022 at 05:37:43PM -0800, Per Bothner wrote: > On 11/30/22 06:44, Gavin Smith wrote: > > There are a couple of other less important problems. You can see > > them at https://www.gnu.org/s

Re: Missing file tta/swig/perl/Texinfo.pm at make dist

On Mon, Jul 28, 2025 at 01:10:56PM +0100, Gavin Smith wrote: > On Sun, Jul 27, 2025 at 10:53:32PM +0100, Gavin Smith wrote: > > Texinfo.pm does not exist in the tta/swig/perl directory, and although > > it is listed in Makefile.am there is no rule to build it. > > Just on the topic of "make dist",

Re: Missing file tta/swig/perl/Texinfo.pm at make dist

On Sun, Jul 27, 2025 at 10:53:32PM +0100, Gavin Smith wrote: > Texinfo.pm does not exist in the tta/swig/perl directory, and although > it is listed in Makefile.am there is no rule to build it. Just on the topic of "make dist", I wonder if it would help to track this file (and others) in git, if i

Re: t/z_misc/*.t tests are a nuisance to update

On Mon, Jul 28, 2025 at 02:14:19AM +0100, Gavin Smith wrote: > > I've added a -g flag to both tests so their results can be updated > with "perl -w t/z_misc/no_structure_test.t -g" etc., which is > tolerable to do for the two tests. I will also add the call to maintain/all_tests.sh with generate.

Re: t/z_misc/*.t tests are a nuisance to update

On Sat, Jul 26, 2025 at 02:06:19AM +0100, Gavin Smith wrote: > I'll then copy the output file to the reference file (copying and > pasting the file names from the output). Then I have to repeat this again > to check that there are no more failures. > > There is a note in t/z_misc/no_structure_tes

Re: Lengthy rebuild after updating CSS rules

On Sun, Jul 27, 2025 at 04:10:32PM +0100, Gavin Smith wrote: > I am going to work on splitting HTMLData.pm. The CSS data is actually > only used in one .c file. Maybe even better would be to have the CSS data and the html_style_commands_element together, and the remaining information in another f

Re: Highlighting with pygments

On 7/27/25 1:13 AM, Patrice Dumas wrote: On Sat, Jul 26, 2025 at 02:42:59PM -0700, Raymond Toy wrote: Or maybe texinfo run pygmentize with extra options? Yes, pygmentize is especially called with -O noclasses=True, probably because I wanted to avoid confusion with Texinfo classes. For the re

Re: Highlighting with pygments

On 7/27/25 1:13 AM, Patrice Dumas wrote: On Sat, Jul 26, 2025 at 02:42:59PM -0700, Raymond Toy wrote: Or maybe texinfo run pygmentize with extra options? Yes, pygmentize is especially called with -O noclasses=True, probably because I wanted to avoid confusion with Texinfo classes. Ahh, that

Re: Lengthy rebuild after updating CSS rules

On Sun, Jul 27, 2025 at 10:50:40AM +0200, Patrice Dumas wrote: > On Sun, Jul 27, 2025 at 09:59:12AM +0200, Patrice Dumas wrote: > > On Sat, Jul 26, 2025 at 11:24:48PM +0100, Gavin Smith wrote: > > > However, I don't know if we could follow their method. Even if we could, > > > it wouldn't make the

Re: Lengthy rebuild after updating CSS rules

On Sun, Jul 27, 2025 at 09:59:12AM +0200, Patrice Dumas wrote: > On Sat, Jul 26, 2025 at 11:24:48PM +0100, Gavin Smith wrote: > > However, I don't know if we could follow their method. Even if we could, > > it wouldn't make the build system any easier to understand. > > What could be possible is

Re: Highlighting with pygments

On Sat, Jul 26, 2025 at 02:42:59PM -0700, Raymond Toy wrote: > I've been experimenting with using pygments to do syntax highlighting. This > works fine, except I can't choose the style to use. I learned that pygments > can output the CSS that controls the formatting and colors. For my example, > I'

Re: Lengthy rebuild after updating CSS rules

On Sat, Jul 26, 2025 at 11:24:48PM +0100, Gavin Smith wrote: > However, I don't know if we could follow their method. Even if we could, > it wouldn't make the build system any easier to understand. I do not really see the issue with rebuilding dependencies of data used for code generation when th

Re: Conflict in CSS 'padding-left' setting for index formatting

On Sun, Jul 27, 2025 at 12:42:09AM +0100, Gavin Smith wrote: > On Sat, Jul 26, 2025 at 11:13:36PM +0100, Gavin Smith wrote: > > On Sat, Jul 26, 2025 at 11:45:53PM +0200, Patrice Dumas wrote: > > Should we add the name of the command, so current > > > > > > > > would become the following? > >

Re: Conflict in CSS 'padding-left' setting for index formatting

On Sat, Jul 26, 2025 at 11:13:35PM +0100, Gavin Smith wrote: > On Sat, Jul 26, 2025 at 11:45:53PM +0200, Patrice Dumas wrote: > > On Sat, Jul 26, 2025 at 10:07:03PM +0100, Gavin Smith wrote: > > > A simple solution would be to avoid outputting the > > > "printindex-index-entry" > > > class for ind

Re: Conflict in CSS 'padding-left' setting for index formatting

On Sat, Jul 26, 2025 at 11:13:36PM +0100, Gavin Smith wrote: > On Sat, Jul 26, 2025 at 11:45:53PM +0200, Patrice Dumas wrote: > > On Sat, Jul 26, 2025 at 10:07:03PM +0100, Gavin Smith wrote: > > > A simple solution would be to avoid outputting the > > > "printindex-index-entry" > > > class for ind

Re: Lengthy rebuild after updating CSS rules

On Sat, Jul 26, 2025 at 02:30:23PM -0700, Raymond Toy wrote: > On 7/25/25 5:34 PM, Gavin Smith wrote: > > > It appears from looking at maintain/generate_code_convert_data.pl that > > there is quite a bit of code in the header file that is generated, included > > but not limited to size of arrays.

Re: Conflict in CSS 'padding-left' setting for index formatting

On Sat, Jul 26, 2025 at 11:45:53PM +0200, Patrice Dumas wrote: > On Sat, Jul 26, 2025 at 10:07:03PM +0100, Gavin Smith wrote: > > A simple solution would be to avoid outputting the "printindex-index-entry" > > class for index subentries and to put all the needed rules on both > > classes. > > It l

Re: Conflict in CSS 'padding-left' setting for index formatting

On Sat, Jul 26, 2025 at 10:07:03PM +0100, Gavin Smith wrote: > A simple solution would be to avoid outputting the "printindex-index-entry" > class for index subentries and to put all the needed rules on both > classes. It looks good to me. It could also be possible to take that opportunity to ad

Re: Lengthy rebuild after updating CSS rules

On 7/25/25 5:34 PM, Gavin Smith wrote: It appears from looking at maintain/generate_code_convert_data.pl that there is quite a bit of code in the header file that is generated, included but not limited to size of arrays. It may not be possible to stop generating this file, or to include it in f

Re: new formatting for printindex in HTML

On Fri, Jul 25, 2025 at 05:41:30PM +0100, Gavin Smith wrote: > I don't agree with specifying "font-size: 150%" for the index letter > headers, as we shouldn't be specifying exact ratios of font sizes. As > I said, the previous formatting looked fine, so we could try to imitate > this, even if we e

Re: new formatting for printindex in HTML

On Fri, Jul 25, 2025 at 05:41:27PM +0100, Gavin Smith wrote: > I am afraid to say that I liked the older formatting better. The > screen shots show the comparison (taken at 200% zoom in Chromium). Not sure that it is really helpful, but I personally find that both are ok in term of esthetics of t

Re: pseudotty.c compilation error

Gavin Smith wrote: > It should be fixed in commit 6e582db42d. Confirmed: The CI reports no regressions, compared to the build two weeks ago. Bruno

Re: pseudotty.c compilation error

Gavin Smith writes: > On the subject of sys/select.h, the libc Texinfo manual appears > to be out of date: > > "A better solution is to use the select function. This blocks the program > until input or output is ready on a specified set of file descriptors, > or until a timer expires, whichever c

Re: pseudotty.c compilation error

On Thu, Jul 24, 2025 at 03:25:03PM -0700, Collin Funk wrote: > Bruno Haible via Bug reports for the GNU Texinfo documentation system > writes: > > > The CI now reports a compilation error on Solaris 11.4, during "make check", > > that was not present 3 days ago: > > > > Making check in info > > m

Re: pseudotty.c compilation error

Bruno Haible via Bug reports for the GNU Texinfo documentation system writes: > The CI now reports a compilation error on Solaris 11.4, during "make check", > that was not present 3 days ago: > > Making check in info > make check-am > make pseudotty > gcc -m64 -DHAVE_CONFIG_H -I. -I../../info -

Re: dependency on libperl?

Patrice Dumas wrote: > > So, it would be good to add an autoconf check similar to the one > > checking for the possibility to embed Perl. I'll probably do it when I > > have time. > > Should be done. I confirm that the Ubuntu and RISCV-cross builds now succeed again. Bruno

Re: dependency on libperl?

On Mon, Jul 21, 2025 at 11:45:15PM +0200, Patrice Dumas wrote: > So, it would be good to add an autoconf check similar to the one > checking for the possibility to embed Perl. I'll probably do it when I > have time. Should be done. -- Pat

Re: dependency on libperl?

Patrice Dumas wrote: > > The second is as a result of the SWIG stuff, which looks like is > > happening here. > > Indeed, there is no proper check of libperl being present ... > > So, it would be good to add an autoconf check similar to the one > checking for the possibility to embed Perl. I'll

Re: compilation error on NetBSD

On Mon, Jul 21, 2025 at 10:42:10PM +0100, Gavin Smith wrote: > On Mon, Jul 21, 2025 at 11:02:17PM +0200, Bruno Haible via Bug reports for > the GNU Texinfo documentation system wrote: > > The CI reports a compilation error on NetBSD 10.0: > > > > gcc -DHAVE_CONFIG_H -I. -I../../info -I.. -I../..

Re: dependency on libperl?

On Mon, Jul 21, 2025 at 10:29:24PM +0100, Gavin Smith wrote: > > Is the mandatory dependency on libperl intended? > > > > Bruno > > It shouldn't depend on libperl. As far as I understand, libperl can come > in two ways (Patrice could confirm this). > > The first is when building the C implement

Re: compilation error on NetBSD

On Mon, Jul 21, 2025 at 11:02:17PM +0200, Bruno Haible via Bug reports for the GNU Texinfo documentation system wrote: > The CI reports a compilation error on NetBSD 10.0: > > gcc -DHAVE_CONFIG_H -I. -I../../info -I.. -I../.. > -I../../gnulib/lib

Re: dependency on libperl?

On Mon, Jul 21, 2025 at 11:05:24PM +0200, Bruno Haible via Bug reports for the GNU Texinfo documentation system wrote: > The CI reports a link error on Ubuntu (both when compiling natively and > when cross-compiling for RISCV), that was not present last week: > > /bin/bash ../../libtool --tag=CC

Re: "make distcheck" failure

Gavin Smith wrote: > Thanks for the report and apologies for the inconvenience. I have fixed > in commit 9ce27563568c (today's date). OK, I'm starting a new CI run (because you certainly want to know if there happen to be other regressions). Bruno

Re: "make distcheck" failure

On Mon, Jul 21, 2025 at 09:04:09PM +0200, Bruno Haible via Bug reports for the GNU Texinfo documentation system wrote: > Hi, > > The CI reports today that, unlike a week ago, "make distcheck" fails: > > (cd info && make top_distdir=../texinfo-7.2.20250721dev > distdir=../texinfo-7.2.20250721d

Re: [PATCH v1 1/1] Short Sample: show how to avoid warning: node `[...]' unreferenced.

On Sat, 19 Jul 2025 14:25:12 +0100 Gavin Smith wrote: > The @menu block you have added is unnecessary in newer versions of > Texinfo and I don't understand what you hope to achieve by adding in > back in. OK, so it's already fixed, thanks a lot, and sorry for the noise. Denis. pgpi_SZD_AUPQ.pg

Re: [PATCH v1 1/1] Short Sample: show how to avoid warning: node `[...]' unreferenced.

On Sat, Jul 19, 2025 at 02:20:36AM +0200, Denis 'GNUtoo' Carikli wrote: > While the current Short Sample work fine, if we remove the second > section and run run the following command: >makeinfo -D "VERSION 0.1" -D "UPDATED now" shortsample.texi' > we end up with the following warning: > sh

Re: Unable to build Texinfo from git ("SWIG not found")

On Fri, Jul 18, 2025 at 06:46:35PM +0200, Andreas Schwab wrote: > > -- Macro: AC_ARG_WITH (PACKAGE, HELP-STRING, [ACTION-IF-GIVEN], > > [ACTION-IF-NOT-GIVEN]) > > > > The option now looks like it was given, so the third argument to > > AC_ARG_WITH, [ with_swig='yes' ], runs, leading to

Re: Highlight syntax with source-highlight produces error with split html output

On Fri, Jul 18, 2025 at 10:27:34AM -0700, Raymond Toy wrote: > Well, dang. I don't get this error anymore either. I didn't change anything. > > Oh, wait. If I remove src-hl_html/, I get the error. But if I run it again, > I don't. And the files are all there as you show. You figured it out. I'm

Re: Highlight syntax with source-highlight produces error with split html output

On 7/18/25 9:47 AM, Gavin Smith wrote: On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: |@include src-hl.c | I changed it to |#include src-hl.c | Now I get the message: |texi2any: warning: highlight_syntax.pm: could not open src-hl_html/src-hl_highlight_C_input.C: No such file o

Re: Highlight syntax with source-highlight produces error with split html output

On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: > |@include src-hl.c | > > I changed it to > > |#include src-hl.c | > > Now I get the message: > > |texi2any: warning: highlight_syntax.pm: could not open > src-hl_html/src-hl_highlight_C_input.C: No such file or directory | > > It a

Re: Unable to build Texinfo from git ("SWIG not found")

On Jul 18 2025, Gavin Smith wrote: > On Thu, Jul 17, 2025 at 02:28:20AM +0100, Gavin Smith wrote: >> The responsible code is in tta/configure.ac: >> >> >> - >> # SWIG interfaces >> >> # FIXME if enable_xs=yes and embedded_p

Re: Highlight syntax with source-highlight produces error with split html output

On 7/18/25 8:56 AM, Gavin Smith wrote: On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: Huh, this is weird. Perhaps I messed up building texinfo 7.2 from sources a while back? Anyway, with your test, I ran it. I get a message that it can't include src-hl.c. That seems to come from

Re: Highlight syntax with source-highlight produces error with split html output

On Fri, Jul 18, 2025 at 08:43:21AM -0700, Raymond Toy wrote: > Huh, this is weird. Perhaps I messed up building texinfo 7.2 from sources a > while back? > > Anyway, with your test, I ran it. I get a message that it can't include > src-hl.c. That seems to come from the line > > |@include src-hl.c

Re: Highlight syntax with source-highlight produces error with split html output

On 7/18/25 7:04 AM, Gavin Smith wrote: On Wed, Jul 16, 2025 at 02:27:25PM -0700, Raymond Toy wrote: I'm experimenting with HIGHLIGHT_SYNTAX=source-highligit. It works fine with --no-split and produces pretty nice highlighting. However, when I don't use --no-split, I get an error. An example er

Re: Unable to build Texinfo from git ("SWIG not found")

On Thu, Jul 17, 2025 at 02:28:20AM +0100, Gavin Smith wrote: > The responsible code is in tta/configure.ac: > > > - > # SWIG interfaces > > # FIXME if enable_xs=yes and embedded_perl=no, the interface will need > # to build

Re: Highlight syntax with source-highlight produces error with split html output

On Wed, Jul 16, 2025 at 02:27:25PM -0700, Raymond Toy wrote: > I'm experimenting with HIGHLIGHT_SYNTAX=source-highligit. It works fine with > --no-split and produces pretty nice highlighting. > > However, when I don't use --no-split, I get an error. An example error > message: > > |makeinfo: warn

Re: Texinfo 7.2 pdf output for @example lisp

On 7/16/25 2:38 PM, Gavin Smith wrote: On Wed, Jul 16, 2025 at 02:13:43PM -0700, Raymond Toy wrote: If I have a texinfo file that has |@example lisp (defun foo (x) (+ x x)) @end example | (The line breaks are not present in the plaintext version of your email). Oops. Sorry! I used the versi

Re: Texinfo 7.2 pdf output for @example lisp

On Wed, Jul 16, 2025 at 02:13:43PM -0700, Raymond Toy wrote: > If I have a texinfo file that has > > |@example lisp (defun foo (x) (+ x x)) @end example | (The line breaks are not present in the plaintext version of your email). > > and do |texinfo --pdf|, (with texinfo 7.2), the pdf output lo

Re: Info hook script for file not found?

On Wed, Jul 16, 2025 at 04:19:53PM +0200, Patrice Dumas wrote: > On Wed, Jul 16, 2025 at 12:57:03AM +0100, Gavin Smith wrote: > > This feature still needs work: > > > > * At what point do we run the hook - before checking for man pages, > > or after? E.g. if "tar.info" is not installed but the ta

Re: Info hook script for file not found?

On Wed, Jul 16, 2025 at 12:57:03AM +0100, Gavin Smith wrote: > This feature still needs work: > > * At what point do we run the hook - before checking for man pages, > or after? E.g. if "tar.info" is not installed but the tar man page > is installed, should "info tar" run the hook, or display the

Re: Info hook script for file not found?

On Sun, Feb 23, 2025 at 03:51:47PM +, Gavin Smith wrote: > I've commited code to use a hook program under > "XDG_CONFIG_DIRS/texinfo/info-hooks/manual-not-found", where XDG_CONFIG_DIRS > could be e.g. $HOME/.config or /etc/xdg. Previous discussion: https://lists.gnu.org/archive/html/bug-texin

Re: Start on replacement for titlepage in texinfo.tex

On Tue, Jul 15, 2025 at 02:27:05PM +0300, Eli Zaretskii wrote: > > It would be good in my opinion to get rid of the @vskip line as it > > looks ugly and confusing and probably turns people off. > > I think this calls for some research: how many manuals do NOT use the > standard @vskip line, and if

Re: Start on replacement for titlepage in texinfo.tex

> From: Gavin Smith > Date: Mon, 14 Jul 2025 21:13:20 +0100 > > On Mon, Jun 30, 2025 at 11:30:30PM +0100, Gavin Smith wrote: > > So just using @maketitle to produce the copyright page too is > > a real possibility. > > So I've been seeing what I can implement in texinfo.tex as a prototype > for

Re: Start on replacement for titlepage in texinfo.tex

> I've also implemented a "@publication" command in texinfo.tex, that > should contain information about the publisher and any other details > specific to the act of publication. [...] This looks nice, thank you. Werner

Re: Start on replacement for titlepage in texinfo.tex

On Mon, Jul 14, 2025 at 09:13:36PM +0100, Gavin Smith wrote: > On Mon, Jun 30, 2025 at 11:30:30PM +0100, Gavin Smith wrote: > > So just using @maketitle to produce the copyright page too is > > a real possibility. > > So I've been seeing what I can implement in texinfo.tex as a prototype > for thi

Re: epsf.tex: New file

(Cc-ing bug-texinfo. Oddly, Gavin and I were just talking about epsf.tex. Bruno's original message: https://lists.gnu.org/archive/html/bug-gnulib/2025-07/msg00083.html) So, the problem is not limited to Bison. It occurs because epsf.tex is a dependency of (in fact, the only dependency of)

Re: Texinfo::Common::debug_print_tree doesn't work well with Texinfo::TreeElement

On Fri, Jul 11, 2025 at 01:15:50PM +0100, Gavin Smith wrote: > > There is the $Data::Dumper::Toaster function in Data::Dumper that could > > be used to do something for each blessed object, maybe copy it without > > blessing? > > It is $Data::Dumper::Freezer that does something before it is > dump

Re: Could texinfo.tex skip re-reading defaults from txi-en.tex ?

On Fri, Jul 11, 2025 at 06:35:04PM +0100, Gavin Smith wrote: > On Fri, Jul 11, 2025 at 07:14:13PM +0200, Sebastian Meyer wrote: > > Would it make sense for texinfo.tex to skip over @documentlanguage en when > > no other language has been set before? > > It seems like it is a special case for not m

Re: Could texinfo.tex skip re-reading defaults from txi-en.tex ?

On Fri, Jul 11, 2025 at 07:14:13PM +0200, Sebastian Meyer wrote: > Now that CTAN no longer contains the translation files (following a recent > thread on this list, > ), the > texinfo bundle from CTAN is no longer sufficient to p

Could texinfo.tex skip re-reading defaults from txi-en.tex ?

Now that CTAN no longer contains the translation files (following a recent thread on this list, ), the texinfo bundle from CTAN is no longer sufficient to process the following minimal Texinfo document \input texinfo

Re: Texinfo::Common::debug_print_tree doesn't work well with Texinfo::TreeElement

On Fri, Jul 11, 2025 at 11:26:19AM +0200, Patrice Dumas wrote: > On Fri, Jul 11, 2025 at 12:45:05AM +0100, Gavin Smith wrote: > > As Texinfo tree elements are now blessed into the Texinfo::TreeElement > > class, this class is output by Data::Dumper when used by > > Texinfo::Common::debug_print_tree

Re: Texinfo::Common::debug_print_tree doesn't work well with Texinfo::TreeElement

On Fri, Jul 11, 2025 at 12:45:05AM +0100, Gavin Smith wrote: > As Texinfo tree elements are now blessed into the Texinfo::TreeElement > class, this class is output by Data::Dumper when used by > Texinfo::Common::debug_print_tree. I use this fairly often when developing > and/or debugging. Sample

Re: why 'verbatim' output for menu comments in HTML?

> I edited the documentation slightly. It should be covered by the > sentence, "Menu comment lines and any empty lines are kept in the > output." Thanks, this looks good. Werner

Re: why 'verbatim' output for menu comments in HTML?

On Wed, Jul 09, 2025 at 07:23:53AM +, Werner LEMBERG wrote: > > >> OK, so please document this. Looking at section `Writing a menu` > >> in the Texinfo info file (of current git) I don't see anything > >> about HTML output of `@menu` blocks and how it is formatted (and > >> the description of

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

>> Ouch! I simply searched for the string 'footer' in the Texinfo >> info pages and I got no hit. I now see that the description of >> `WORDS_IN_PAGE` is in the 'Customization of Navigation and Headers' >> section (as it should be), which I missed. > > You could also have checked the indices w

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

On Wed, Jul 09, 2025 at 05:04:34AM +, Werner LEMBERG wrote: > Ouch! I simply searched for the string 'footer' in the Texinfo info > pages and I got no hit. I now see that the description of > `WORDS_IN_PAGE` is in the 'Customization of Navigation and Headers' > section (as it should be), whic

Re: ugly page break in ToC

>> Both are OK to me. However, what I have a problem with are cases >> where too much empty vertical space remains, which could be easily >> filled with a chapter entry and four lower-level entries, say. > > I've made a change changing this dimension down to 30pt. Thanks. > I know you said yo

Re: why 'verbatim' output for menu comments in HTML?

>> OK, so please document this. Looking at section `Writing a menu` >> in the Texinfo info file (of current git) I don't see anything >> about HTML output of `@menu` blocks and how it is formatted (and >> the description of `FORMAT_MENU` doesn't mention this either). > > In general, we do not d

Re: why 'verbatim' output for menu comments in HTML?

On Wed, Jul 09, 2025 at 06:18:15AM +, Werner LEMBERG wrote: > > Hello Patrice and Gavin, > > > thanks for your answers. > > >> Why ``? I consider this surprising since the item description > >> of a menu entry (i.e., the third part of an entry) is not output > >> with ``. > > > > The idea

Re: script for updating CSS entities

>> Maybe you can provide a list of the most important CSS changes, or >> maybe add a section that describes how to do the transition to >> Texinfo 7.0 and newer? > > Here is what is in tta/TODO (which is more notes than TODO). We > have not formally described that in the Texinfo manual because we

Re: script for updating CSS entities

On Wed, Jul 09, 2025 at 06:36:08AM +, Werner LEMBERG wrote: > Maybe you can provide a list of the most important CSS changes, or > maybe add a section that describes how to do the transition to Texinfo > 7.0 and newer? Here is what is in tta/TODO (which is more notes than TODO). We have not f

Re: script for updating CSS entities

>> Comparing the HTML of version 6.8 with version 7.2, I see that many >> classes got new names. This means that we essentially have to >> rewrite our custom CSS file, which is not fun. >> >> What about providing a script >> >> ``` >> texinfo-css-update --from 6.8 --to 7.2 < infile > outfile >> ``

Re: why 'verbatim' output for menu comments in HTML?

Hello Patrice and Gavin, thanks for your answers. >> Why ``? I consider this surprising since the item description >> of a menu entry (i.e., the third part of an entry) is not output >> with ``. > > The idea was that the users may have wanted to have the end lines > and spaces to be signific

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

>> What must I do to always get a navigation panel in the footer >> (i.e., `NODE_FOOTER_BUTTONS`)? > > texi2any --html -c FORMAT_MENU=menu -c WORDS_IN_PAGE=0 test.texi > > The setting of FORMAT_MENU is immaterial. Thanks! > This question has been asked so many times before that I wonder if >

Re: script for updating CSS entities

On Tue, Jul 08, 2025 at 10:53:39PM +0100, Gavin Smith wrote: > and the one I found was this: > > https://lilypond.org/doc/v2.25/Documentation/css/lilypond-manuals.css > > If that is the only CSS file, then it seems plausible that we could work > together on what would have to be updated. I'm afr

Re: script for updating CSS entities

On Tue, Jul 08, 2025 at 12:19:58PM +, Werner LEMBERG wrote: > > Comparing the HTML of version 6.8 with version 7.2, I see that many > classes got new names. This means that we essentially have to rewrite > our custom CSS file, which is not fun. > > What about providing a script > > ``` > te

Re: script for updating CSS entities

On Tue, Jul 08, 2025 at 12:19:58PM +, Werner LEMBERG wrote: > > Comparing the HTML of version 6.8 with version 7.2, I see that many > classes got new names. This means that we essentially have to rewrite > our custom CSS file, which is not fun. > > What about providing a script > > ``` > te

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

On Tue, Jul 08, 2025 at 07:42:13PM +, Werner LEMBERG wrote: > > [texi2any 6.8, 7.2] > > > texi2any --html -c FORMAT_MENU=menu menu.texinfo > ``` > > There is only a header but no footer navigation panel. > > What must I do to always get a navigation panel in the footer (i.e., > `NODE_FOOT

Re: why 'verbatim' output for menu comments in HTML?

On Tue, Jul 08, 2025 at 12:07:11PM +, Werner LEMBERG wrote: > > [texi2any 7.2] > > > texi2any --html -c FORMAT_MENU=menu menu.texinfo > ``` > > the menu comment in output file `index.html` gets formatted like this: > > ``` > > > > XXX yyy ZZZ > > > > ``` > > Why ``? I consider thi

Re: why 'verbatim' output for menu comments in HTML?

On Tue, Jul 08, 2025 at 12:07:11PM +, Werner LEMBERG wrote: > > [texi2any 7.2] > > > Consider the following example file `menu.texinfo`. > > ``` > \input texinfo > > @node Top > @top Top > > @menu > * Foo:: Foo foo foo. > > > XXX @var{yyy} ZZZ > > > * Bar:: Bar bar bar. > @end menu >

Re: how to get HTML navigation panel in footer with `-c FORMAT_MENU=menu`

On Tue, Jul 08, 2025 at 07:42:13PM +, Werner LEMBERG wrote: > There is both a header and a footer navigation panel. However, the > files `Foo.html` and `Bar.html` look like the following: > > ``` > Previous: Foo, Up: Top > --- > > ... > > ``` > > There is only a

Re: ugly page break in ToC

On Mon, Jul 07, 2025 at 06:08:37PM +, Werner LEMBERG wrote: > > I am not really sure which is better. There is more in chapter 17 > > and one argument is that it is better to start a new page for > > chapter 17's contents listing. > > Both are OK to me. However, what I have a problem with ar

Re: ugly page break in ToC

>> Thanks, this helps: for my version of the LilyPond Notation >> Reference a value of 10pt works just fine. Before that I tried >> 20pt, however, I got a different but equally bad gap as reported >> originally. This makes me wonder whether we are we really turning >> the right screw... > > I tr

Re: ugly page break in ToC

>> While playing around with adding parts to LilyPond's Notation >> Reference, I got the attached layout in the ToC. As can be seen, >> there is a vertical gap corresponding to approx. 8 lines(!) at the >> bottom of page vi; I've never noticed such a large gap before in any >> Texinfo document. [

Re: better PDF formatting of `@part` in ToC

>> I played around a bit more, and I think it looks good if the >> vertical space right before the part entry gets increased a bit, >> see attached image. > > I think it will be safest to keep the same size for the text, > and just to use increased spacing before the part line to separate > it v

Re: wrong to use Index match in Info reader for the presence of index?

On Sun, Jun 29, 2025 at 11:55:11PM +0200, Patrice Dumas wrote: > On Sat, Jun 28, 2025 at 07:54:36PM +0100, Gavin Smith wrote: > > > I checked that a tag that is not 'Node:' or 'Ref:' has the Info reader > > > (but not the Emacs Info reader) stop going through tags immediatly. > > > This means that

Re: ugly page break in ToC

On Mon, Jul 07, 2025 at 06:10:52AM +, Werner LEMBERG wrote: > > [texinfo.tex 2025-03-22.08] > [luatex Version 1.22.0 (TeX Live 2025), Development id: 7673] > > > While playing around with adding parts to LilyPond's Notation > Reference, I got the attached layout in the ToC. As can be seen,

  1   2   3   4   5   6   7   8   9   10   >