On Sun, Nov 06, 2022 at 04:09:59PM +, Werner LEMBERG wrote:
> * Let's assume that GNU awk behaves similar to, say, GNU sort. The
> collation order and input encoding gets controlled with `LANG` –
> looking into the awk info manual this seems like a reasonable
> assumption.
>
> As far
On Tue, Nov 08, 2022 at 07:48:20AM -0800, Raymond Toy wrote:
> On most html manuals that I've looked at that have split the manual into
> multiple html pages, I see a navbar (next/previous/up) at the top of each
> page and also at the bottom.
>
> However, once in a while I see pages where the bot
On Tue, Nov 08, 2022 at 04:58:39PM +, Gavin Smith wrote:
> I suspect this is related to the following change:
Exactly. And other similar crashes may happen. I tried to check the
code as much as possible to avoid them, but I have probably missed some.
> 2022-09-17 Patrice
On Tue, Nov 08, 2022 at 04:58:39PM +, Gavin Smith wrote:
> Patrice, would you be able to look at this?
Fixed in
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=fc756d9128170d92cfacb367e2622c991b1ea5c7
--
Pat
On Tue, Nov 08, 2022 at 04:58:39PM +, Gavin Smith wrote:
>
> I suspect at one time the contents should have been set to an empty
> array, so that the code would have worked. It would be easy
> to add an extra check for the contents being defined, but I wonder
> how much other code there is li
On Tue, Nov 08, 2022 at 11:07:51PM +0100, Vincent Lefevre wrote:
>
> Well, let's try. :-)
>
>
> \input texinfo@c -*-texinfo-*-
>
> @tex
> \gdef\texatan{\mathop{\rm atan}}
> @end tex
>
> @iftex
> @macro atan
> \\mathop{\\rm atan}
>
On Tue, Nov 08, 2022 at 02:02:46PM -0800, Raymond Toy wrote:
> On Tue, Nov 8, 2022 at 8:34 AM Gavin Smith wrote:
>
> >
> > Can you check the output from "automake --version" as I believe older
> > automake required "@setfilename" in Texinfo files.
> >
>
> It says 1.15.1. On a different linux box
On Fri, Nov 11, 2022 at 08:47:32AM +, Werner LEMBERG wrote:
>
> [texinfo.tex 2022-11-07.17]
>
>
> I suggest to change the mapping for U+00B0 (DEGREE SIGN) to use
> `@textdegree{}`.
>
> ```
> \input texinfo
>
> @code{45°}
>
> @code{45@textdegree{}}
>
> @bye
> ```
It is better to be consi
On Fri, Nov 11, 2022 at 10:34:05AM -0800, Raymond Toy wrote:
> The following examples were built using texinfo 6.8 (haven't upgraded to 7
> yet). No custom css is used.
>
> Look at
> https://cmucl.org/docs/cmu-user/html/More-About-Types-in-Python.html#More-About-Types-in-Python
> on a mobile devi
On Sat, Nov 12, 2022 at 09:27:34AM +0200, Eli Zaretskii wrote:
> See that "Bugs" at the end? This is the problem: since "Bugs" is a
> top-level node, its presence in a level-1 node's menu makes the node
> tree not really a tree, so Backspace loops.
>
> Thus, the problem is in the way Gnuplot prod
On Sat, Nov 12, 2022 at 12:40:11PM +0100, Vincent Lefevre wrote:
>
> But "down" is the reverse of "up". So, if you know all the "up"
> relations, you can deduce all the "down" relations, i.e. all the
> children. Then the issue is to sort the children, but I suppose
> that this could be done by loo
On Sat, Nov 12, 2022 at 10:26:54PM +, Gavin Smith wrote:
>
> Commit 15ef3457ed1 (on release branch)
>
> This led to test result changes in
> tp/t/results/sectioning/unnumbered_before_top_node.pl
> tp/t/results/preformatted/titlefont_in_example.pl
>
> which weren't on the master branch - in b
On Sat, Nov 12, 2022 at 11:53:19PM +0100, Patrice Dumas wrote:
> On Sat, Nov 12, 2022 at 10:26:54PM +, Gavin Smith wrote:
> >
> > Commit 15ef3457ed1 (on release branch)
> >
> > This led to test result changes in
> > tp/t/results/sectioning/unnumbered_be
On Sat, Nov 12, 2022 at 10:26:54PM +, Gavin Smith wrote:
> While other changes since the last release may be valuable, I don't see
> that they are urgent. Please discuss it if there's anything vital that
> people think that should be included.
>
I think that the following change should be in
On Sat, Nov 12, 2022 at 11:25:04PM +, Gavin Smith wrote:
> > I can do that change/commit on the 7.0 branch.
>
> OK that's fine. You can either do
>
> git cherry-pick b238da561dad6
>
> and then to remove parts of the commit, do
>
> git reset --soft HEAD^
>
> followed by
>
> git reset .
>
On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote:
> I've done it myself. I didn't change the makeinfo invocation. I don't
> like the "-c TEXINFO_OUTPUT_FORMAT=plaintexinfo" option much but it is
> not a big deal if you would rather use it. (My feeling is that
> "plaintexinfo" is not v
Hello,
For LaTeX output, it seems important to allow to customize the
beginning of the preamble, with the documentclass and usepackage.
The remaining of the generated preamble can probably be undone/modified
by LaTeX code in a @latex block appearing in the preamble, before any
formatted content, t
On Sun, Nov 13, 2022 at 11:53:54AM +, Gavin Smith wrote:
> On Sun, Nov 13, 2022 at 12:26:33PM +0100, Patrice Dumas wrote:
> > On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote:
> > > I've done it myself. I didn't change the makeinfo invocation.
On Sun, Nov 13, 2022 at 07:45:44PM +, Gavin Smith wrote:
> When I run "make distcheck", there are two test failures:
I think that I just fixed that, by chance while looking at something
else, the issue is that the tested init files were not in DIST.
https://git.savannah.gnu.org/cgit/texinfo.gi
On Thu, Nov 17, 2022 at 09:01:31PM +, Gavin Smith wrote:
> I have tracked tp/Makefile.tres in git both to avoid distcheck failures
> when one of us adds a new test, and to make switching branches easier.
>
> I know tracking generated files is always tricky, so please report if
> there are prob
the generated html broke this.
Yes:
2022-03-11 Patrice Dumas
* doc/texinfo.texi @code{@@settitle}): no title in the
document anymore in the default case in HTML.
It was redundant with the @top.
--
Pat
On Fri, Nov 18, 2022 at 04:12:23PM -0800, Per Bothner wrote:
>
>
> On 11/18/22 15:48, Patrice Dumas wrote:
> > On Fri, Nov 18, 2022 at 03:19:23PM -0800, Per Bothner wrote:
> > >
> > >
> > > Before, when I converted the DomTerm manual to html the
On Fri, Nov 18, 2022 at 05:40:51PM -0800, Per Bothner wrote:
> On 11/18/22 14:43, Gavin Smith wrote:
> > Unfortunately, it has various obvious problems. Most significantly, the
> > index search does not work.
>
> The problem is line 1459 in info.js:
>
> var index_links = document.queryS
Hello,
Some formatting for @subentry, @seenentry and @seealso in HTML more in
line with TeX output has been implemented in the developpement source:
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=76485d9ea1f8e411b6b4e4196babe1089d286a42
https://git.savannah.gnu.org/cgit/texinfo.git/comm
On Sat, Nov 19, 2022 at 04:09:05AM -0800, Per Bothner wrote:
>
>
> We really shouldn't be using ' ' or empty table cells for formatting.
> Use CSS. For example:
>
>
> span.index-entry-level-1 {padding-left: 2em }
> td.printindex-index-section { padding-left: 1em }
>
I have modified span.i
Hello,
I find the colon produced between index entries and nodes/sections in
printindex HTML formatting to be quite ugly, and uneeded, as the table
is already providing the structure. Is it only me?
What about setting it to '' in the default case?
(It is alreadu '' in the texi2html style).
--
On Sat, Nov 19, 2022 at 09:30:30AM -0800, Per Bothner wrote:
>
>
> On 11/19/22 08:58, Patrice Dumas wrote:
> > I have modified span.index-entry-level-1 to use padding-left instead of
> > margin-left, but to have some space between the td elements, shouldn't
>
On Sat, Nov 19, 2022 at 04:09:05AM -0800, Per Bothner wrote:
>
> On 11/19/22 01:22, Patrice Dumas wrote:
> > Any proposition for a better formatting? Any idea on how to help
> > javascript-ing, maybe with a custom attribute with the full entry with
> > commas separating t
On Sun, Nov 20, 2022 at 10:49:06AM +, Gavin Smith wrote:
> On Sat, Nov 19, 2022 at 08:35:34PM +0100, Patrice Dumas wrote:
> > I think that it is less practical than padding-left, I will use
> > padding-left as you initially suggested.
>
> We have to be careful about rely
On Sun, Nov 20, 2022 at 11:07:34AM -0800, Raymond Toy wrote:
>
> Thank you so much for working on this! It looks way better and more useful
> than the old way.
>
> The only issue I have is that the subentries aren't indented enough. I
> think it would be easier to read if they were indented by
On Sun, Nov 20, 2022 at 11:33:53AM -0800, Raymond Toy wrote:
> On Sun, Nov 20, 2022 at 11:24 AM Patrice Dumas wrote:
> > On small screens a level two subentry would lead to too much
> > indentation. But using 2 and 4 would already indent much more. I'll
> > see if it
On Sun, Nov 20, 2022 at 01:35:33PM -0800, Per Bothner wrote:
> Before I do that, I suggest cleaning up the generated html a bit, as
> discussed:
> - Get rid of the dummy table cells used for indentation.
The first column is the letter column. It is not really indentation,
although it indeeds le
On Sun, Nov 20, 2022 at 11:30:08AM -0800, David Bacon wrote:
> The following command on the attached .texi file never terminates, but
> spins while consuming more and more memory until it is killed:
>
> $ makeinfo --html --no-split --no-headers setl-lib.texi
Thanks for the report.
I'll have a lo
On Mon, Nov 21, 2022 at 07:07:05AM -0800, David Bacon wrote:
> Wow, well done, reducing it to such a nice tidy little test case!
Actually the smallest case is the following (which I thought we tested
for...):
@node sharp
@section @ref{sharp} tuple
> I'm sure you've also realized by now that I li
On Mon, Nov 21, 2022 at 09:12:56PM +0100, Patrice Dumas wrote:
> On Mon, Nov 21, 2022 at 07:07:05AM -0800, David Bacon wrote:
> > Wow, well done, reducing it to such a nice tidy little test case!
>
> Actually the smallest case is the following (which I thought we tested
> f
On Sun, Nov 20, 2022 at 02:05:15PM -0800, Per Bothner wrote:
>
>
> On 11/20/22 13:47, Patrice Dumas wrote:
> > On Sun, Nov 20, 2022 at 01:35:33PM -0800, Per Bothner wrote:
> > > Before I do that, I suggest cleaning up the generated html a bit, as
> > > discus
On Mon, Nov 21, 2022 at 01:42:20PM -0800, David Bacon wrote:
> But I like such constructs! I have one in every one of the 249 @section
> commands in the document I originally submitted with the bug report. They
> are there so that the Table of Contents in the PDF has a nice link from the
> name o
On Tue, Nov 22, 2022 at 12:16:44AM +0100, Patrice Dumas wrote:
>
> In term of implementation, it could indeed be solved in the converters.
Should be done in
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=89594d63e7f5fa0796be4c0002d6200219ef5e62
@Gavin, I think that it should go
Hello,
Not sure about that as I am not a native english speaker. When a
@*table does not have an @-command formatter for the items, the error
message is
d.texi:2: table requires an argument: the formatter for @item
This message seems fine to me if there is no argument for @*table,
however, if t
On Sat, Dec 10, 2022 at 03:11:47PM +, Gavin Smith wrote:
> On Sat, Dec 10, 2022 at 11:34:47AM +, Gavin Smith wrote:
> > The commands were clearly based on the corresponding LaTeX commands,
> > which we should take as authoritative. LaTeX \verb doesn't break on
> > a space, so Texinfo @verb
Hello,
On Sat, Dec 17, 2022 at 01:28:21PM -0700, arn...@skeeve.com wrote:
> Hi.
>
> I'd like to request a feature.
>
> I would like to have
>
> @sidebar Sidebar Title Here
>
> @end sidebar
This looks like @cartouche in Texinfo. The difference is that
@cartouche never ha
Hello,
With @inline* commands, it is rather easy to mix raw output with Texinfo
within paragraphs. With output format block commands such as @html, it
is also possible to mix blocks without starting paragraphs. However,
there is no way to mix raw output with Texinfo outside of paragraph and
bloc
On Mon, Dec 19, 2022 at 10:51:00PM +, Gavin Smith wrote:
> On Mon, Dec 19, 2022 at 10:30:04PM +0100, Patrice Dumas wrote:
> > Hello,
> >
> > With @inline* commands, it is rather easy to mix raw output with Texinfo
> > within paragraphs. With output format block
On Tue, Dec 20, 2022 at 05:30:22PM +, Gavin Smith wrote:
> On Tue, Dec 20, 2022 at 12:02:30AM +0100, Patrice Dumas wrote:
>
> It can be done if there are no special characters in the title:
Actually, I completely forgot that @-commands are expanded in output
format raw blocks. Th
On Thu, Dec 15, 2022 at 02:32:12PM -0800, Per Bothner wrote:
> When using the js-info reader, the location bar displays these URLs for nodes:
> https://domterm.org/Wire-byte-protocol.html (if http/https)
> file:///home/bothner/DomTerm/web/index.html#Wire-byte-protocol (if file:)
> These are als
Hello,
If I recall well, there was some previous discussions, I believe Gavin
proposed something similar.
As it is now --enable-encoding (ENABLE_ENCODING customization option)
means something very different for Info/Plaintext and HTML/XML based
formats. For Info/Plaintext is means using actual c
On Sun, Dec 25, 2022 at 10:03:51PM +, Gavin Smith wrote:
> On Sun, Dec 25, 2022 at 10:45:04PM +0100, Patrice Dumas wrote:
> > Hello,
> >
> > If I recall well, there was some previous discussions, I believe Gavin
> > proposed something similar.
> >
&
On Sat, Dec 03, 2022 at 01:41:44AM +, Gavin Smith wrote:
> Not a big deal but I noticed that nested @ignore does not work with
> texi2any, although it does work with texinfo.tex. For example:
Indeed, @ignore are implemented like @verbatim. However, @macro which
is in the same block commands
On Tue, Dec 27, 2022 at 12:56:50PM +0100, Patrice Dumas wrote:
> On Sat, Dec 03, 2022 at 01:41:44AM +, Gavin Smith wrote:
> > Not a big deal but I noticed that nested @ignore does not work with
> > texi2any, although it does work with texinfo.tex. For example:
>
>
On Fri, Dec 30, 2022 at 11:11:52AM +0100, Hilmar Preuße wrote:
> Hello,
>
> the lintian checker in Debian reports, that the manual page of
> texi2dvi.1 has a bad whatis entry. It refers to the output of lexgrog,
> which fails to parse.
>
> hille@sid-amd64:~/devel/TeXLive/github/texinfo$ lexgrog t
On Wed, Dec 28, 2022 at 10:06:54PM +, Gavin Smith wrote:
> > I have done it, but I am not so happy with the result. Indeed, nested
> > @ignore now appears in the tree, but the tree is quite complicated for a
> > case of an ignored block. Maybe it would be better not to have an
> > explicit el
On Thu, Dec 29, 2022 at 10:59:43AM -0800, Raymond Toy wrote:
> Consider the following table (taken in part from maxima's user manual):
>
> @multitable {greater than or equal to 333} {notequal 333} {relational
> function}
> @headitem Operation @tab Symbol @tab Type
> @item less than
On Thu, Dec 29, 2022 at 11:06:45AM -0800, Raymond Toy wrote:
> One other thing. Each item from headitem is left-justified for both info
> and pdf. But it's centered in html. For consistency, should they all be
> left-justified? (Or maybe allow a way to control that? It looks funny in
> html if
On Sun, Jan 01, 2023 at 06:49:38PM +, Gavin Smith wrote:
> Making check in tests
> mksh: Fatal error: The string `included_lan1.texi' is not valid in
> current locale
> Current working directory: /export/home/g/texinfo-7.0.1/tp/tests
>
> ( is a single byte).
>
> This is in a UTF-8 locate.
>
On Tue, Jan 03, 2023 at 09:28:03PM +, Gavin Smith wrote:
> On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> > One way of fixing this might be to put the generated file in a
> > subdirectory so that make can't see it. Or it might not be worth
> > bothering as this version of make
On Wed, Jan 04, 2023 at 12:44:45PM +, Gavin Smith wrote:
> On Wed, Jan 04, 2023 at 01:31:22PM +0100, Patrice Dumas wrote:
> > On Tue, Jan 03, 2023 at 09:28:03PM +, Gavin Smith wrote:
> > > On Mon, Jan 02, 2023 at 03:46:56PM +, Gavin Smith wrote:
> > > > O
On Mon, Jan 02, 2023 at 09:39:33AM -0800, Raymond Toy wrote:
> On Sun, Jan 1, 2023 at 10:12 AM Patrice Dumas wrote:
>
> > I do not remember any discussion about that. But it is not clear to me
> > what should be done. There is no obvious way to get the width of
> &g
On Mon, Jan 02, 2023 at 09:44:39AM -0800, Raymond Toy wrote:
> On Sun, Jan 1, 2023 at 10:19 AM Patrice Dumas wrote:
>
> Thanks, this should work. I was just wondering if texinfo should be more
> consistent in the output since the PDF output has left-aligned columns, as
> does
Hello,
For those who follow the source version control, I changed the directories in
tp/tests, which should require running ./autogen.sh to get things right,
otherwise there may not be errors but still some tests would be ignored.
--
Pat
On Wed, Jan 04, 2023 at 06:40:08PM +, Gavin Smith wrote:
> I ran autogen.sh and there is another test failure:
>
> $ perl -w t/09indices.t index_table
> ok 1
> ok 2 - index_table tree
> ok 3 - index_table sectioning
> ok 4 - index_table nodes
> ok 5 - index_table menus
> ok 6 - index_table err
On Wed, Jan 04, 2023 at 07:44:57PM +, Gavin Smith wrote:
> $ ls t/results/indices/index_table/out_plaintext/index_table.txt/
> indices-refs.txt node-with-printindex.txt
> node-with-ftable-and-vtable.txt Top.txt
>
> After I do
>
> $ rm -r t/results/indices/index_table/out_plai
/ChangeLog b/ChangeLog
> index d416b25a45..5821561f47 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,10 @@
> +2023-01-06 Torbjörn Svensson
> +
> + * tp/Texinfo/Common.pm (output_files_initialize, output_files_open_out):
> + Add warning when paths conflicts on a case
On Fri, Jan 06, 2023 at 09:52:34PM +, Gavin Smith wrote:
> On Fri, Jan 06, 2023 at 08:47:52PM +0100, Patrice Dumas wrote:
> > On Fri, Jan 06, 2023 at 01:28:04PM +0100, Torbjörn SVENSSON wrote:
> > > Hi,
> > >
> > > I can't find where to send p
On Sat, Jan 07, 2023 at 09:52:17AM +0100, Torbjorn SVENSSON wrote:
>
> Okay, maybe I was unclear in the first mail.
> What I'm doing is building the manual on a GNU/Linux system with a case
> sensitive file system. This means that the build is fine and there is no way
> for the makeinfo command to
On Sat, Jan 07, 2023 at 11:41:36AM +0100, Torbjorn SVENSSON wrote:
>
>
> If this is clear that I should have been using the
> CASE_INSENSITIVE_FILENAMES setting, why is it not always active?
Because it produces suboptimal manuals in case sensitive filesystems.
> I, as a user, would expect to ha
On Mon, Jan 09, 2023 at 08:03:52AM +0100, Torbjorn SVENSSON wrote:
>
>
> On 2023-01-07 16:05, Patrice Dumas wrote:
> > That'd be nice, indeed. Beware that the issue can happen between
> > redirection pages, and also between regular elements and redirection
> >
On Mon, Jan 09, 2023 at 09:57:45AM +0100, Patrice Dumas wrote:
>
> Actually, it could be that redirection pages clash with element file
> names because of transliteration, for example the following names would
> clash:
> @node Près
> @anchor{Prés}
It is indeed the case, I adde
On Mon, Jan 09, 2023 at 08:00:38PM +0100, Torbjorn SVENSSON wrote:
>
>
> Feel free to do it if you have time right now for it or I can try to take a
> stab at it in a few days.
Actually it is probably better if I do it in any case, as gathering
which command lead to a given file name is gonna be
Hello,
Here is a commit which should bring in explicit error messages about
conflicts among redirection pages and with other output files:
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=2d279f1d39bf026eeb243beb9f00aecb0b0bf2d2
Still need to set CASE_INSENSITIVE_FILENAMES=1 for case inse
On Wed, Jan 11, 2023 at 06:35:01PM +0100, Torbjorn SVENSSON wrote:
>
>
> On 2023-01-11 08:48, Patrice Dumas wrote:
> > Hello,
> >
> > Here is a commit which should bring in explicit error messages about
> > conflicts among redirection pages and w
On Fri, Jan 13, 2023 at 09:01:41PM +, Gavin Smith wrote:
> I've checked the important output formats (texinfo.tex, HTML, Info, DocBook,
> LaTeX) and it seems that there isn't much more to be done on either @w or
> @verb to get consistency across the output formats.
>
> The main thing I found w
On Fri, Jan 13, 2023 at 11:22:14PM +, Gavin Smith wrote:
>
> Something like it appears to be possible with CSS:
>
>
>
> greater than or equal to 333
> notequal 333
> relational function
>
> OperationSymbolType
> less than
> less than or equal to class="code"><=relationa
On Fri, Jan 13, 2023 at 11:25:59PM +, Gavin Smith wrote:
> On Fri, Jan 13, 2023 at 11:10:31PM +0100, Patrice Dumas wrote:
> > If I recall well, the idea was that even an empty @w{} would lead to
> > some output such that if within a string, the string would not end eup
> &
On Fri, Jan 13, 2023 at 09:01:41PM +, Gavin Smith wrote:
>
> Are there any thoughts on the change at the bottom of this mail?
Actually, it is not ok, if there is an @-command within the @w, the
spaces used in formatting will be replaced too. Need to add a
state and do the substitution in the
On Sat, Jan 14, 2023 at 10:19:53AM +, Gavin Smith wrote:
> On Sat, Jan 14, 2023 at 10:41:10AM +0100, Patrice Dumas wrote:
> > It seems that the portability of "visibility: collapse" and
> > implementation is not good, and that it would be better to use
&g
On Tue, Jan 17, 2023 at 09:26:54PM +, Gavin Smith wrote:
> Disclaimer: this message is not immediately practical.
>
> One thing I've noticed is that direct nesting of @ref commands is diagnosed,
> but indirect nesting is not:
Indeed, this is a long-standing issue in texi2any, and should be,
n
On Wed, Jan 18, 2023 at 08:54:21PM +, Gavin Smith wrote:
> On Wed, Jan 18, 2023 at 11:52:33AM +0100, Patrice Dumas wrote:
> > Even the recent one? I started having more categories in command_data.txt
> > both for the inner commands classes (in_heading_spec) and outer comman
On Wed, Jan 18, 2023 at 09:30:53PM +, Gavin Smith wrote:
> I don't see why it should be a huge performance barrier. Suppose
> we want to forbid nested @footnote; then we would have a hash like
> $self->{'nesting_context'} equal to {'footnote' => 0}, then when
> we enter a @footnote, we increme
On Sat, Jan 21, 2023 at 12:50:37PM +, Gavin Smith wrote:
> On Thu, Jan 19, 2023 at 04:52:07AM +0100, Patrice Dumas wrote:
> > It is not completly clear to me that the performance cost would be lower
> > than looking at the commands stack and checking that the nesting is
> &g
On Sun, Jan 22, 2023 at 09:19:30PM +, Gavin Smith wrote:
> On Sat, Jan 21, 2023 at 03:12:15PM +0100, Patrice Dumas wrote:
> > Please commit, I'll change the perl parser afterwards, it looks very
> > easy to implement. I have a commit related to source marks ready that I
&
On Wed, Jan 25, 2023 at 01:59:02PM +0100, Arsen Arsenović wrote:
> * tp/Texinfo/ParserNonXS.pm (_check_valid_nesting_context): Escape
> invalid uses of @.
> ---
> Hi,
>
> I was building the Git version of Texinfo and noticed this minor typo.
> OK for master?
Yes, please commit.
>
> Thanks in ad
On Thu, Jan 26, 2023 at 01:45:00PM +0100, Arsen Arsenović wrote:
> * doc/texi2any_api.texi (Basic Formatting Customization): Document
> the new $target argument of format_heading_
> * tp/Texinfo/Convert/HTML.pm (_default_format_heading_text): Add
> optional target argument, for generating a copiabl
On Thu, Jan 26, 2023 at 08:32:21PM +0100, Patrice Dumas wrote:
>
> Lastly, for consistency, I think that it is better to use only " for the
> attributes, I can do it too.
This one is not on you, it is like that for all copiable anchors...
I'll change it anyway.
--
Pat
On Wed, Jan 25, 2023 at 08:33:06PM +, Gavin Smith wrote:
> On Wed, Jan 18, 2023 at 11:52:33AM +0100, Patrice Dumas wrote:
> > Even the recent one? I started having more categories in command_data.txt
> > both for the inner commands classes (in_heading_spec) and outer comman
On Sun, Jan 29, 2023 at 06:57:32PM +, Gavin Smith wrote:
>
> I've started work on this in the patch below.
Looks right to me.
> When I have time, I will make the corresponding change to the XS code.
> Then it should be straightforward to extend this to all commands
> that should only contain
On Sun, Feb 05, 2023 at 08:47:02PM +, Gavin Smith wrote:
> In the above list, I see no need for any of:
> @sp, @verbatiminclude, @set, @clear and @vskip.
For @set and @clear, it is in the manual, in the @code{@@set @@value}
node:
However, unlike most other commands which take the rest of
th
On Mon, Feb 06, 2023 at 07:17:27AM +, Gavin Smith wrote:
> On Sun, Feb 05, 2023 at 11:31:55PM +0100, Patrice Dumas wrote:
> > On Sun, Feb 05, 2023 at 08:47:02PM +, Gavin Smith wrote:
> > > In the above list, I see no need for any of:
> > > @sp, @verbatiminclu
On Fri, Feb 03, 2023 at 08:19:16PM +, Gavin Smith wrote:
>
> %contain_basic_inline_with_refs_commands
>
> This contains sectioning and heading commands, so that
>
> @section Changes in @ref{SubModule}
>
> is allowed. I found this mail in the archives with the rationale
> for allowing su
On Wed, Feb 08, 2023 at 09:43:55PM +, Gavin Smith wrote:
> Tested with git commit 0fb51499dd.
>
> TEXINFO_XS=require perl -w t/60macro.t
>
> often produces a test failure in the 'macro_in_def_delimiters' test.
> It does not happen every time so I suspect a memory error.
>
> TEXINFO_XS=requir
On Sat, Feb 11, 2023 at 05:04:45PM +, Gavin Smith wrote:
> I found that texi2any was significantly slower than expected on a
> manual.
>
> I ran with Devel::NYTProf:
>
> TEXINFO_XS=require perl -d:NYTProf ../texi2any.pl
> ../../../emacs-lispref-27.2/elisp.texi
>
> The flame graph output sho
On Mon, Feb 13, 2023 at 08:47:26AM +, Gavin Smith wrote:
> > Other than that I do not have much other idea than disabling it, for
> > instance if documentlanguage is en. The result with Unicode::Collate is
> > better for accented letters, but not so useful in english. There could
> > even be
On Mon, Feb 13, 2023 at 08:47:26AM +, Gavin Smith wrote:
> > Other than that I do not have much other idea than disabling it, for
> > instance if documentlanguage is en. The result with Unicode::Collate is
> > better for accented letters, but not so useful in english. There could
> > even be
Hello,
That's probably because an empty last arg does not get contents.
Smallest reproducer is probably
@macro Defesc{a, b}
\b\
@end macro
@Defesc {a, }
I should be able to fix it soon.
On Mon, Feb 13, 2023 at 06:43:37PM +, Gavin Smith wrote:
> git revision 5151d8232b68ba8d8a, 2023-02-13
May be fixed in
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=606f3c94201213524b0f1a776b559126dfc973c9
But not sure that it is exactly the same error as the one valgrind
reports.
--
Pat
On Mon, Feb 13, 2023 at 06:43:37PM +, Gavin Smith wrote:
> git revision 5151d8232b68ba8d8a,
On Tue, Feb 14, 2023 at 07:24:57PM +, Gavin Smith wrote:
> For example, in the main menu in the bash manual:
>
> * Job Control:: What job control is and how Bash allows you
> to use it.
>
> In the Texinfo source, this node could be defined like
On Sat, Jan 21, 2023 at 10:27:22AM +, Gavin Smith wrote:
>
> I think index commands should close any open paragraphs, as there is no other
> way of getting the right output other than having a blank line.
What about preformatted? I think that index entries should not stop
preformatted, such
On Wed, Feb 22, 2023 at 06:44:03PM +, Gavin Smith wrote:
> Link to previous discussion:
>
> > https://lists.gnu.org/archive/html/automake-patches/2022-12/msg0.html
> > https://lists.gnu.org/archive/html/bug-texinfo/2022-12/msg00076.html
>
> The summary is that words with apostrophes, like
On Wed, Feb 22, 2023 at 07:28:10PM +, Gavin Smith wrote:
> On Wed, Feb 22, 2023 at 06:44:05PM +, Gavin Smith wrote:
> > Hence, what I propose is adding a new variable (ASCII_GLYPH or similar)
> > for the first point, set to false by default. ASCII_PUNCTUATION would
> > only affect the seco
On Fri, Feb 24, 2023 at 06:57:40PM +0100, Arsen Arsenović wrote:
> Hi Gavin,
>
> Gavin Smith writes:
>
> > Yes please. After you commit this I will cherry-pick to the release
> > branch as this is a severe bug in install-info. I had never tested it
> > as root, only with a regular user account
On Mon, Feb 27, 2023 at 10:14:17PM +, Gavin Smith wrote:
> On Thu, Feb 23, 2023 at 11:50:35AM +0100, Arsen Arsenović wrote:
> > I like this. I think that tables are quite ergonomic, and so having
> > @defblocks look like them should be okay.
> >
> > > The next step is to get copiable anchors
1 - 100 of 1773 matches
Mail list logo
