On Sat, Jul 24, 2021 at 03:06:40AM +0100, Sam James wrote:
> They appear to be fixed upstream in gnulib - there's a variety of commits [1]
> which solve conflicting macros. Following README-hacking, I updated gnulib
> to commit c567dcac24dd90a2be051772d9a8c8bbf869221a there and texinfo builds!
>
On Fri, Jul 23, 2021 at 11:47:56PM +0200, René Neumann wrote:
> b) I suggest printing out an error message instead of (or in addition to) a
> full abort. As one can see in the reddit, it leaves the user puzzled and
> needs installation of debug symbols to figure out the reason.
I've stopped it
On Fri, Jul 23, 2021 at 11:47:56PM +0200, René Neumann wrote:
> Hi *,
>
> as reported on Reddit [1], there is an issue with the pt_BR translation of
> texinfo that leads to an abort.
>
> One function name is replaced with a typo in the translation:
> [get-inffo-help-node]
>
> This was
On Sat, Jul 24, 2021 at 03:06:40AM +0100, Sam James wrote:
> They appear to be fixed upstream in gnulib - there's a variety of commits [1]
> which solve conflicting macros. Following README-hacking, I updated gnulib
> to commit c567dcac24dd90a2be051772d9a8c8bbf869221a there and texinfo builds!
>
On Wed, Jul 07, 2021 at 04:52:43AM +0900, Norbert Preining wrote:
> Hi Gavin, hi all,
>
> thanks a lot, I did put texinfo 6.8 into Debian/experimental for now
> since we are in deep freeze before release.
>
> One comment, pushing this version to my packaging repo on github I got a
> lot of
On Tue, Jul 6, 2021 at 2:09 PM Ken Brown wrote:
> It was just reported on the Cygwin mailing list that makeinfo can't be used
> in a
> pipeline any more:
>
>https://cygwin.com/pipermail/cygwin/2021-July/248849.html
>
> I assume this is not an intentional change.
It wasn't: it is due to the
On Mon, Jul 05, 2021 at 06:09:37PM +0200, Patrice Dumas wrote:
> On Mon, Jul 05, 2021 at 11:36:55AM +0100, Gavin Smith wrote:
> >
> > Yes I agree, if we can't make the test pass in the case that no locales
> > are installed.
> >
> > It's a frustrating prob
On Mon, Jul 05, 2021 at 10:57:21AM +0100, Chris Clayton wrote:
> > This isn't what I expected as you have a locale "en_US.utf8" which I
> > understand is the same thing as "en_US.UTF-8", which is one of the
> > locales tried in 'gdt' in tp/Texinfo/Report.pm.
>
> That's not a surprise to me. My
> If it is this part of the code that
> is causing the test failure then it would be due to upgrading the
> bundled version of libintl-perl, due to a fix for the issue at
> https://rt.cpan.org/Public/Bug/Display.html?id=81315
>
> I reported the issue here
>
On Sun, Jul 4, 2021 at 7:04 PM Chris Clayton wrote:
> Thanks for the reply, Gavin.
>
> Right, thanks. the two commands give:
>
> $ locale
> LANG=en_GB.UTF-8
> LC_CTYPE="en_GB.UTF-8"
> LC_NUMERIC="en_GB.UTF-8"
> LC_TIME="en_GB.UTF-8"
> LC_COLLATE="en_GB.UTF-8"
> LC_MONETARY="en_GB.UTF-8"
>
On Sun, Jul 04, 2021 at 10:34:23AM +0100, Chris Clayton wrote:
> Hi,
>
> I'm trying to build the latest texinfo release. The compile/link phase ends
> OK, but make test fails thusly:
>
> SKIP: test_scripts/tex_html_math_not_closed.sh
> SKIP: test_scripts/tex_html_tex_not_closed.sh
> PASS:
We have released version 6.8 of Texinfo, the GNU documentation format.
This package contains tools to produce documentation in various
formats, including HTML and PDF, from source files in the Texinfo
format. Texinfo is a text-based format with commands for marking text,
document structuring and
On Thu, Jul 01, 2021 at 10:03:12AM +0900, Norbert Preining wrote:
> Hi all,
>
> On Thu, 01 Jul 2021, Gavin Smith wrote:
> > > Have been looking at the `TEXMF=/usr/share/texmf install-tex` problem.
> > > The
> > > conclusion from installing texinfo
On Wed, Jun 30, 2021 at 8:08 PM Christopher Dimech wrote:
>
>
> Felicitations Gavin. Am very appreciative of the significant improvements
> to texinfo.
>
> Have been looking at the `TEXMF=/usr/share/texmf install-tex` problem. The
> conclusion from installing texinfo has been the difficulty in
The next pretest for the next Texinfo release has been uploaded to
https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.92.tar.xz
We hope to release this in a few days' time barring the discovery of
any major issues.
There are minimal changes since the last pretest; we have made it to
make a pretest
On Tue, Jun 22, 2021 at 01:54:07PM -0700, Per Bothner wrote:
> I tested out the js-info browser in a DomTerm browser window:
> $ domterm --tab browser URL-TO-MANUAL
> That failed, because domterm creates the requested browser window in an
> iframe (interior frame).
> Luckily the fix is easy:
On Fri, Jun 18, 2021 at 8:00 PM Eli Zaretskii wrote:
>
> > Date: Fri, 18 Jun 2021 21:47:26 +0300
> > From: Eli Zaretskii
> > Cc: bug-texinfo@gnu.org
> >
> > > The main way to check would be to set TEXINFO_XS=debug in the environment
> > > and check that the modules are being loaded.
> >
> > How
On Fri, Jun 18, 2021 at 09:19:54PM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Fri, 18 Jun 2021 16:34:42 +0100
> > Cc: bug-texinfo@gnu.org
> >
> > > This pretest builds cleanly with MinGW on MS-Windows, and passes all
> > > the t
On Fri, Jun 18, 2021 at 04:07:23PM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Tue, 15 Jun 2021 21:44:54 +0100
> >
> > The next pretest for the next Texinfo release has been uploaded to
> >
> > https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.9
On Fri, Jun 18, 2021 at 06:52:40AM -0700, Per Bothner wrote:
>
>
> On 6/18/21 6:07 AM, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Tue, 15 Jun 2021 21:44:54 +0100
> > >
> > > The next pretest for the next Texinfo release has been uploa
On Thu, Jun 17, 2021 at 10:26 AM Benno Schulenberg wrote:
>
>
> Op 17-06-2021 om 01:52 schreef Gavin Smith:
> > Thanks, I made these changes.
>
> Oww... The
>
> msgid "Try `%s --help' for more information\n
>
> needs a period at the end:
>
> ms
On Wed, Jun 16, 2021 at 11:54:03AM +0200, Benno Schulenberg wrote:
>
> Op 15-06-2021 om 22:44 schreef Gavin Smith:
> > https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.91.tar.xz
>
> msgid "try `%s --help' for more information\n"
>
> Please change this to:
>
The next pretest for the next Texinfo release has been uploaded to
https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.91.tar.xz
We hope to release this fairly soon barring the discovery of any major issues.
Summary of changes since previous pretest (6.7.90, 2021-02-23):
* some fixes of indentation
It has been a while since the last pretest release (23rd February) and
I would like to do another one soon (probably in the next week, when I
get a few hours to run tests and so on). There have not been a lot of
changes recently but please think if there are changes that should be
made,
On Wed, Mar 10, 2021 at 11:35:53PM +0100, Bruno Haible wrote:
>
> When you look into the files MiscXS.c, TestXS.c, XSParagraph.c (search for
> PERL_VERSION in there) you can see that
>
> * The generated C code needs to be dependent on the Perl version,
> * xsubpp has produced code that is
On Tue, Apr 27, 2021 at 04:39:58AM +, Werner LEMBERG wrote:
>
> >> ```
> >> \input texinfo.tex
> >>
> >> @node Top
> >>
> >> @node Foo
> >> @chapter Foo
> >>
> >> @image{image,,,image} test
> >>
> >> bar
> >>
> >> @image{image,,,image} test
> >>
> >> baz
> >>
> >> @bye
> >
> > I don't
On Thu, May 06, 2021 at 10:09:04PM -0400, Nathaniel Beaver wrote:
> Steps to reproduce:
> Compile with -fsanitize=address, then run:
>
> info -f reproduce_bug.info
>
> Expected behavior:
>
> info does not trigger AddressSanitizer errors.
>
> Actual behavior:
>
> AddressSanitizer reports a
On Thu, May 13, 2021 at 10:14:11AM +0300, Eli Zaretskii wrote:
> I needed to rebuild Texinfo-6.7 after the OS upgrade, so I did "make
> distclean" in the top-level directory. For some reason, this didn't
> remove gnulib/lib/locale.h, which was produced by the last build on
> the old OS, and that
On Thu, Jun 03, 2021 at 10:45:12PM +0200, Patrice Dumas wrote:
> On Tue, Jun 01, 2021 at 07:04:57PM +0100, Gavin Smith wrote:
> > I did an interview with Joshua Branson where we discussed many issues
> > around Texinfo, may be of interest to some.
> >
> > https://video
I did an interview with Joshua Branson where we discussed many issues
around Texinfo, may be of interest to some.
https://video.hardlimit.com/videos/watch/a10761b7-f6e2-472a-be06-69b0bfbcfe9d
On Mon, May 31, 2021 at 9:38 PM Augusto Stoffel wrote:
> Well, yes, it _explains_ the issue. But why not solve the issue?
It explains why it is hard to solve the issue.
> > Yes, but how do I get a plain link, with no extra markup?
> >
> > You can't. Info is a plain text format that is
This question comes up again and again and the following was added to
the manual to address this. I hope it explains the issue.
Why do I have 'see' appearing in front of all of my links?
By default, Emacs Info mode either changes the marker '*note' for
cross-references to 'see', or
> On 5/6/21 12:36 PM, Gavin Smith wrote:
> > On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
> >> It seems wrong to include inline css in generated html files,
> >> especially when using the --ccs-ref or -C INFO_JS_DIR options.
> >> The documentati
On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
> It seems wrong to include inline css in generated html files,
> especially when using the --ccs-ref or -C INFO_JS_DIR options.
> The documentation is complicated. The advice to use !important
> to override the default style rules feels
On Sat, Feb 20, 2021 at 05:43:55PM -0500, Nathaniel Beaver wrote:
> Steps to reproduce:
> Compile with -fsanitize=address, then run:
>
> info -f reproduce_bug.info
>
> Expected behavior:
>
> info does not trigger AddressSanitizer errors.
>
> Actual behavior:
>
> AddressSanitizer reports a
On Sun, Apr 18, 2021 at 03:16:52AM +1000, G. Branden Robinson wrote:
> [following up after nearly a year]
>
> At 2020-05-27T23:37:29+1000, G. Branden Robinson wrote:
> > Hi Gavin,
> >
> > Please accept my apologies for the delay. I kept wanting to produce a
> > reduced version of the groff
On Sun, May 02, 2021 at 03:09:19PM -0700, Per Bothner wrote:
>
>
> On 5/2/21 2:16 PM, Gavin Smith wrote:
> > I've noticed something else (sorry, don't know how hard it would be
> > to fix). When on a page that has sub-sections in the same page (due
> > to the leve
On Sun, May 02, 2021 at 10:17:43AM -0700, Per Bothner wrote:
>
>
> On 5/2/21 10:10 AM, Gavin Smith wrote:
> > I saw that you've commited a change to this but it is not reflected for
> > me at
> >
> > https://per.bothner.com/tmp/Kawa-txjs-plain/style/info.js
&g
On Sun, May 02, 2021 at 08:26:14AM -0700, Per Bothner wrote:
>
>
> On 4/30/21 4:06 AM, Per Bothner wrote:
> >
> >
> > On 4/29/21 9:40 AM, Gavin Smith wrote:
> > > Another problem: Navigate to
> > >
> > > https://per.bothner.c
On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
> It seems wrong to include inline css in generated html files,
> especially when using the --ccs-ref or -C INFO_JS_DIR options.
> The documentation is complicated. The advice to use !important
> to override the default style rules feels
On Thu, Apr 29, 2021 at 08:58:47AM -0700, Per Bothner wrote:
> Please try https://per.bothner.com/tmp/Kawa-txjs-plain/index.html
> It has an index. The 'i' command works seems to work nicely
> (after fixing one minor typo).
> --
> --Per Bothner
> p...@bothner.com http://per.bothner.com/
On Thu, Apr 29, 2021 at 08:56:16AM -0700, Per Bothner wrote:
> I implemented the following.
> Pleae try https://per.bothner.com/tmp/Kawa-txjs-plain/index.html
>
> This uses default texinfo styling, without any Kawa/DomTerm-specific tweaks.
> Note the "Hide sidebar" text is now vertical, which I
On Thu, Apr 29, 2021 at 07:15:27PM +0300, Eli Zaretskii wrote:
> One possible aspect for improvement: the way the input field for Index
> search is placed it obscures other text, and there doesn't seem to be
> a way of getting rid of it if I decide not to type anything into that
> field.
You get
On Tue, Apr 27, 2021 at 12:43:22PM -0700, Per Bothner wrote:
> So if I understand you correctly, you would prefer:
> * If the sidebar is hidden, the only way to show it is to click
> on the "Show sidebar" button. (Perhaps we could add a keybinding as well.)
> * Navigating by clicking in the
On Tue, Apr 27, 2021 at 09:59:59AM -0700, Per Bothner wrote:
> I didn't get any feedback on changes mentioned in my 3/22 message,
> but checked it in belatedly just now
>
> To see the effect see
> https://per.bothner.com/tmp/DomTerm-txjs-plain (default GNU styling)
>
On Mon, Apr 26, 2021 at 05:40:35AM +, Werner LEMBERG wrote:
> Note, however, that there are still two problems with inline images.
> Consider the following example.
>
> ```
> \input texinfo.tex
>
> @node Top
>
> @node Foo
> @chapter Foo
>
> @image{image,,,image} test
>
> bar
>
>
On Sun, Apr 25, 2021 at 08:51:38PM +0100, Gavin Smith wrote:
> On Sun, Apr 25, 2021 at 01:08:07PM +0100, Gavin Smith wrote:
> > I haven't worked out where the extra newline should be output and it could
> > take me a while to do this, and I don't know if I will have time anytime
&
On Sun, Apr 25, 2021 at 01:08:07PM +0100, Gavin Smith wrote:
> I haven't worked out where the extra newline should be output and it could
> take me a while to do this, and I don't know if I will have time anytime
> soon to work this out, so help on this would be appreciated.
I've made
On Mon, Mar 22, 2021 at 10:58:09AM +0100, Vitezslav Crhonek wrote:
> From 3d9e36af398e05f50fdd6ca72f2371f493fe6b45 Mon Sep 17 00:00:00 2001
> From: Vitezslav Crhonek
> Date: Wed, 17 Mar 2021 11:58:34 +0100
> Subject: [PATCH 7/8] Fix memory leak
>
> This is done at the end of the function,
On Sun, Apr 25, 2021 at 02:55:38PM +, Werner LEMBERG wrote:
> Please modify either `texinfo.tex` or the info source code to make the
> behaviour identical (whatever it is, I actually don't care).
I agree that this should be done.
> From 9da6053e115e8abc07f8c877dde2d39af0c5101f Mon Sep 17 00:00:00 2001
> From: Vitezslav Crhonek
> Date: Wed, 17 Mar 2021 11:30:43 +0100
> Subject: [PATCH 2/8] Fix memory leak
>
> info_add_extension() returns new string based on 'dirname'. But that
> is the last usage of 'dirname' in the
On Fri, Apr 16, 2021 at 08:46:30PM +, Werner LEMBERG wrote:
>
> [commit 2a15ed35d]
>
>
> Consider this example file `foo.texi`
>
> ```
> @node Top
>
> @image{test,,,foo,}
>
> bar
>
> baz
>
> @bye
> ```
>
> If processed with
>
> makeinfo `foo.texi`
>
> and viewed with `info
On Thu, Apr 22, 2021 at 10:13:10AM +0300, Eli Zaretskii wrote:
> > From: Peng Yu
> > Date: Wed, 21 Apr 2021 19:48:36 -0500
> >
> > It seems that info may just print manpage if the infopage is not
> > available. Is there a way to just let it fail if it doesn't find the
> > infopage instead of
On Thu, Apr 22, 2021 at 9:04 PM Gavin Smith wrote:
> If you could explain what the use case was for an image inserted
> inside text, I might try to see if it could be achieved in TeX using a
> @macro.
I came up with the following which you could try, based on an earlier
file you s
On Mon, Apr 19, 2021 at 8:21 AM Werner LEMBERG wrote:
> * Another optional argument to @image
>
> @image{FILENAME[, WIDTH[, HEIGHT[, ALTTEXT[, EXTENSION[, OFFSET]}
>
> to vertically offset an inline image relative to the vertical origin
> as set by `@imagevertorigin`. OFFSET
On Sun, Apr 11, 2021 at 12:24:07PM +0200, Werner LEMBERG wrote:
>
> [XeTeX 3.141592653-2.6-0.93 (TeX Live 2021)]
> [texinfo 2021-04-08.19]
>
> Consider the following example file `test.texi` (image file
> `image.pdf` is attached):
>
> ```
> \input texinfo
>
> test test test test test test
On Thu, Apr 08, 2021 at 08:35:16PM +0200, Werner LEMBERG wrote:
>
> [texinfo.tex version 2021-03-18.20]
>
>
> Consider the following example.
>
> ```
> \input texinfo
>
> 1
> A
> A
>
> 1
> @iftex
> A
> @end iftex
> A
>
> @bye
> ```
>
> In the attached output it can be seen that the
On Fri, Mar 19, 2021 at 09:20:15PM +0100, Werner LEMBERG wrote:
> Thanks for the explanation. What I conclude is that changing the way
> `@columnfractions` works would break too much documents. Alas, using
> prototypes is not always practicable.
>
> I thus suggest that you introduce a new
On Tue, Mar 23, 2021 at 08:58:54PM +0100, Jonas Hahnfeld wrote:
> I can confirm this works for "@unnumberedsubsec ßa" with XeTeX on
> Ubuntu 16.04.
Is that the version of XeTeX that Werner reported the problem for?
> However, would it be valid input from the user to do @ss in the texi
> file?
On Mon, Mar 22, 2021 at 08:24:20PM +0100, Werner LEMBERG wrote:
>
> Compiling
>
> \input texinfo.tex
>
> @documentencoding UTF-8
>
> @node ß
> @unnumberedsubsec ß
>
> @bye
>
> makes xetex from TeXLive 2015 abort with
>
> ! Extra @else.
> @txiescapepdf ...hisisundefined @xdef
On Mon, Mar 22, 2021 at 6:54 PM Per Bothner wrote:
>
>
>
> On 3/22/21 11:33 AM, Gavin Smith wrote:
> > On Mon, Mar 22, 2021 at 6:13 PM Per Bothner wrote:
> >> There should be a triple-right-arrow in a button-box in the top-left
> >> of the page. If you're
On Mon, Mar 22, 2021 at 6:13 PM Per Bothner wrote:
> There should be a triple-right-arrow in a button-box in the top-left
> of the page. If you're not seeing that, perhaps it's a font issue.
> When you see the sidebar with the "Hide sidebar" text, there should be
> a triple-left-arrow above the
On Mon, Mar 22, 2021 at 5:02 PM Per Bothner wrote:
> Please try:
> https://per.bothner.com/tmp/DomTerm-txjs (DomTerm styling)
> https://per.bothner.com/tmp/DomTerm-txjs-plain (default info styling)
A couple things I noticed:
On the second link, once you click to hide the sidebar there is no way
On Wed, Mar 17, 2021 at 08:20:26PM +, Gavin Smith wrote:
> > In the table below, it is expected that column fractions with
> > identical values cause table columns with the same width. However,
> > this is not true, as the image shows.
> I think it's due to the space
On Sun, Mar 14, 2021 at 09:59:52PM +0100, Werner LEMBERG wrote:
>
> [texinfo.tex version 2021-02-20.11]
>
>
> Please have a look at the attached example. As you can see, the
> `@multitable` environment within a `@quotation` environment sticks out
> to the right, which I consider as
On Wed, Mar 17, 2021 at 03:35:11PM -0700, Edwin Kofler wrote:
> Greetings,
>
> For the info program, it would be useful to have some "INFOKEY_FILE"
> environment variable that
> behaves similar to the '--init-file` option, so the configuration is read
> when info is
> launched from environments
On Wed, Mar 17, 2021 at 08:14:30PM +0100, Werner LEMBERG wrote:
>
> [texinfo.tex version 2021-02-20.11]
>
>
> In the table below, it is expected that column fractions with
> identical values cause table columns with the same width. However,
> this is not true, as the image shows.
>
> This
On Sun, Mar 14, 2021 at 09:59:52PM +0100, Werner LEMBERG wrote:
>
> [texinfo.tex version 2021-02-20.11]
>
>
> Please have a look at the attached example. As you can see, the
> `@multitable` environment within a `@quotation` environment sticks out
> to the right, which I consider as
On Thu, Mar 04, 2021 at 09:20:53PM -0600, Jacob Bachmeyer wrote:
> Per Bothner wrote:
> > On 3/4/21 12:16 PM, Gavin Smith wrote:
> > > On Wed, Mar 03, 2021 at 08:25:59PM -0600, Jacob Bachmeyer wrote:
> >
> > > > The texinfo tool that generates HTM
On Mon, Mar 01, 2021 at 12:18:44PM +0800, 積丹尼 Dan Jacobson wrote:
> >>>>> "GS" == Gavin Smith writes:
> GS> but in any case this should be
> GS> directed towards a list for Emacs development (emacs-de...@gnu.org) as
> GS> that is where the develop
On Sat, Feb 27, 2021 at 09:19:28PM +, Gavin Smith wrote:
> On Sat, Feb 27, 2021 at 04:57:45PM +0100, Bruno Haible wrote:
> > Therefore I think it will be better to prefer 'gawk' to 'awk' in the
> > configure
> > test. That is, change
> > AC_CHECK_PRO
On Wed, Mar 03, 2021 at 02:27:09PM -0800, Per Bothner wrote:
> On 3/3/21 2:00 PM, Gavin Smith wrote:
> > On Tue, Feb 16, 2021 at 03:46:46PM -0800, Per Bothner wrote:
> > > * Hide "Script license information" link or move it to "Help" page.
> > > It's
On Thu, Mar 04, 2021 at 06:03:17PM +0100, Patrice Dumas wrote:
> I am not very knowledgable on that, but I fear that splitting the :
> would make translating quite difficult. Another option could be to use
> markup to remove the need for a :.
If Per got it working I will hold off on this change
On Wed, Mar 03, 2021 at 05:28:46PM -0800, Per Bothner wrote:
> I think the js-info-based version of the DomTerm manual is now
> ready to replace the docbook-based version. (Through probably not until
> after the texinfo release.)
This is really good to hear and the new web site looks very nice.
On Wed, Mar 03, 2021 at 08:25:59PM -0600, Jacob Bachmeyer wrote:
> Per Bothner wrote:
> > [...]
> > Ideally, one could determine which links are internal by checking for an
> > entry in the table-of-contents. However, that is bit complicated,
> > mainly because sub-pages don't have access to the
On Tue, Feb 16, 2021 at 03:46:46PM -0800, Per Bothner wrote:
> * Hide "Script license information" link or move it to "Help" page.
> It's clutter that I don't want on my website, though I might be
> ok with it in the help page.
It could be hidden with CSS as it has the "rel" attribute to identify
On Wed, Mar 03, 2021 at 08:09:01AM -0800, Per Bothner wrote:
> The JavaScript info reader calls the fix_links function to convert
> cross-references to special "magic" links that load a different page
> (or scroll within the current one). "External" references are unchanged,
> except the 'target'
On Tue, Mar 02, 2021 at 04:37:52PM +0100, Patrice Dumas wrote:
> On Tue, Mar 02, 2021 at 02:51:51PM +0000, Gavin Smith wrote:
> > On Tue, Mar 02, 2021 at 01:31:37PM +0100, Benno Schulenberg wrote:
> > >
> > > Hello Gavin,
> > >
> > > Op 23-02-2021 om
On Tue, Mar 02, 2021 at 01:31:37PM +0100, Benno Schulenberg wrote:
>
> Hello Gavin,
>
> Op 23-02-2021 om 22:12 schreef Gavin Smith:
> > The first pretest for the next Texinfo release has been uploaded to
> >
> > https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.90.tar
On Mon, Mar 1, 2021 at 4:46 PM Bruno Haible wrote:
> > Is there any way of turning this off?
>
> Yes: In your configure.ac, after the invocation of gl_INIT, add an assignment
>
> GNULIB_MDA_FDOPEN=0
>
> > https://lists.gnu.org/archive/html/bug-gnulib/2020-12/msg00220.html
> >
> > It says in
On Mon, Mar 01, 2021 at 04:33:15PM +0200, Eli Zaretskii wrote:
> ...exactly: mine is a 32-bit build, where both long and a pointer are
> 32-bit wide. But in a 64-bit build on Windows long is 32-bit and a
> pointer is 64-bit wide, so I think that would emit a warning. Thus, I
> think using
I'm not sure if it's a good idea but in any case this should be
directed towards a list for Emacs development (emacs-de...@gnu.org) as
that is where the development of Info mode is done.
On Wed, Feb 24, 2021 at 12:20 AM 積丹尼 Dan Jacobson wrote:
>
> Let's say we are reading some INFO page, like
>
On Sat, Feb 27, 2021 at 02:41:57PM +0100, Bruno Haible wrote:
> > So, the cause is that an autogenerated and platform-dependent 'texindex'
> > script was included in the tarball. Removing it from the tarball will fix
> > the issue.
>
> Another way to find this problem is: After unpacking the
On Sat, Feb 27, 2021 at 12:11:05PM +0200, Eli Zaretskii wrote:
> Nothing is ever simple with MinGW builds...
Thanks for testing it anyway, it's very unlikely that the issues would
get fixed otherwise.
> 1. There are multiple compilation warnings due to Gnulib's redefining of
> fdopen. Two
On Sat, Feb 27, 2021 at 04:57:45PM +0100, Bruno Haible wrote:
> Therefore I think it will be better to prefer 'gawk' to 'awk' in the configure
> test. That is, change
> AC_CHECK_PROGS([TI_AWK], [awk mawk gawk], [])
> to
> AC_CHECK_PROGS([TI_AWK], [gawk awk mawk], [])
>
> Note: The Autoconf
On Sat, Feb 27, 2021 at 08:30:59PM +, Gavin Smith wrote:
> I don't think there would be an issue with using LC_ALL instead of
> LC_MESSAGES as that is what was done before commit fc28011fb6b34bb
> (on 2020-11-29).
I've commited a change to use LC_ALL instead.
On Sat, Feb 27, 2021 at 02:27:31PM -0600, Jacob Bachmeyer wrote:
> Gavin Smith wrote:
> > On Sat, Feb 27, 2021 at 12:22:33PM +0100, Bruno Haible wrote:
> > > > https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.90.tar.xz
> > > A VPATH build on Solaris 10, with Sola
On Sat, Feb 27, 2021 at 12:11:05PM +0200, Eli Zaretskii wrote:
> 3. Finally, an error that stopped the build:
>
> if TEXINFO_DEV_SOURCE=1 ; export TEXINFO_DEV_SOURCE ; top_srcdir=".." ;
> export top_srcdir ; top_builddir=".." ; export top_builddir ;
> /d/usr/Perl/bin/perl ../tp/texi2any
On Sat, Feb 27, 2021 at 12:11:05PM +0200, Eli Zaretskii wrote:
> 2. A compilation warning in api.c:
>
> parsetexi/api.c: In function 'element_to_perl_hash':
> parsetexi/api.c:431:26: warning: cast from pointer to integer of
> different size [-Wpointer-to-int-cast]
>431 |
On Sat, Feb 27, 2021 at 12:22:33PM +0100, Bruno Haible wrote:
> > https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.90.tar.xz
>
> A VPATH build on Solaris 10, with Solaris 'make', fails during "make check":
>
> Making check in texindex
> make check-TESTS
> FAIL: tests/ti-helpversion.sh
>
> Why is
On Tue, Feb 23, 2021 at 02:29:04PM -0800, Per Bothner wrote:
> It seems the problems Gavin reported were with domterm-specfic
> "extra styling", but using the plan "info.css" works ok.
> So should I check in the changes I made to info.js/info.css?
> I can leave out the special styling rules for
The first pretest for the next Texinfo release has been uploaded to
https://alpha.gnu.org/gnu/texinfo/texinfo-6.7.90.tar.xz
The most significant changes since the last release (September 2019)
are to the texi2any conversion program. There are changes to the HTML
output, including support for
On Tue, Feb 23, 2021 at 01:30:41AM +0100, Patrice Dumas wrote:
> Hello,
>
> It seems confusing to me have %formats_table in texi2any.pl and also access
> to converter default configuration values in %converter_defaults, which
> are used in parser for example. The 'module' key, 'texi2dvi_format',
On Sat, Feb 20, 2021 at 10:03:49PM -0800, Per Bothner wrote:
> I think I've gotten my changes to the js-info reader to a state where it
> can be checked in. See attachment.
>
> In addition to the a "Hide sidebar"/"Show sidebar" button (lower left),
> there is also magic to handle narrows screen
On Sun, Feb 21, 2021 at 09:41:44AM +, Gavin Smith wrote:
> On Sat, Feb 20, 2021 at 02:21:07PM -0800, Per Bothner wrote:
> > On 2/20/21 10:23 AM, Gavin Smith wrote:
> > > On Thu, Feb 18, 2021 at 08:03:22AM -0800, Per Bothner wrote:
> > > > http://per.bothner.
On Sun, Feb 21, 2021 at 12:21:23AM +0100, Patrice Dumas wrote:
> On Sat, Feb 20, 2021 at 10:05:16PM +0000, Gavin Smith wrote:
> > On Sat, Feb 20, 2021 at 05:18:18PM +0100, Patrice Dumas wrote:
> > > This is not easy to determine which warning to output since the node is
> &g
On Sat, Feb 20, 2021 at 02:21:07PM -0800, Per Bothner wrote:
> On 2/20/21 10:23 AM, Gavin Smith wrote:
> > On Thu, Feb 18, 2021 at 08:03:22AM -0800, Per Bothner wrote:
> > > http://per.bothner.com/tmp/DomTerm-txjs/Wire-byte-protocol.html
> >
> > On that page,
On Sat, Feb 20, 2021 at 05:43:55PM -0500, Nathaniel Beaver wrote:
> Steps to reproduce:
> Compile with -fsanitize=address, then run:
>
> info -f reproduce_bug.info
>
> Expected behavior:
>
> info does not trigger AddressSanitizer errors.
>
> Actual behavior:
>
> AddressSanitizer reports a
On Sun, Feb 21, 2021 at 12:40:40AM +0100, Patrice Dumas wrote:
> Hello,
>
> Just tried
>
> ./texi2any.pl -c CHECK_NORMAL_MENU_STRUCTURE=1 test_b.texi
>
> And I get a warning
> ignoring parser configuration value "CHECK_NORMAL_MENU_STRUCTURE"
>
> It is from
>
On Sat, Feb 20, 2021 at 05:18:18PM +0100, Patrice Dumas wrote:
> This is not easy to determine which warning to output since the node is
> automatically added during output. I think that we have two
> possibilities,
> * pass to Structuring.pm the information that nodes will be generated
>
1001 - 1100 of 2308 matches
Mail list logo
