> From: Gavin Smith
> Date: Wed, 10 Apr 2024 23:53:31 +0100
>
> I agree that the warning is not really necessary. I don't mind
> either way. It's up to you if you want to try to remove the warning.
> It's questionable whether lone @node without a following sectioning
> command is proper
> Date: Wed, 10 Apr 2024 21:57:19 +0200
> From: Patrice Dumas
>
> 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 Top
> @top
> Date: Tue, 26 Mar 2024 23:20:23 +0100
> From: Patrice Dumas
>
> > I took the list and tried to sort it into sections. I may not have
> > done an especially good job of this, and there will likely be misplaced
> > variables. I suggest this could be taken as a starting point for
> >
> From: Gavin Smith
> Date: Mon, 5 Feb 2024 19:35:59 +
>
> I found it was being rebuilt by "make" because a dependency was updated:
>
> $ ls -l gnulib/lib/iconv_open-aix.gperf
> -rw-rw-r-- 1 g g 1.8k Jan 31 18:24 gnulib/lib/iconv_open-aix.gperf
>
> which came from a gnulib update to
> From: Gavin Smith
> Date: Sun, 4 Feb 2024 15:58:28 +
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
>
> 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 colla
> Date: Sun, 4 Feb 2024 11:42:52 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , bug-texinfo@gnu.org
>
> On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > I think en_US.utf-8 is (or at least can be by default) a combination
> > of @documentlan
> From: Gavin Smith
> Date: Thu, 1 Feb 2024 22:16:07 +
> Cc: Patrice Dumas , bug-texinfo@gnu.org
>
> 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
> > >
> &
> 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.
> > Swedish) that the user may wish to use instead. Hence, it may be
> > a good
> From: Gavin Smith
> Date: Wed, 31 Jan 2024 20:10:56 +
>
> It seems like a pretty obscure interface. It is barely
> documented - newlocale is in the Linux Man Pages but not the
> glibc manual, and strxfrm_l was only in the Posix standard
>
> Date: Fri, 19 Jan 2024 16:30:33 -0700
> From: Karl Berry
>
> Hi Gavin,
>
> The problem as I remember it was that the error messages are awful:
>
> No argument, but having any message at all is infinitely better than
> silence. I urge you to restore them by default, suboptimal as they
> From: No Wayman
> Date: Thu, 18 Jan 2024 10:52:17 -0500
>
>
> makeinfo --version: texi2any (GNU texinfo) 7.1
> Run on Arch Linux
>
> Reproduction steps:
>
> 1. Clone the "emacs-eat" repository:
>
> $ cd /tmp/
> $ git clone https://codeberg.org/akib/emacs-eat.git
>
> 2. Within the
> Date: Wed, 17 Jan 2024 14:55:33 -0700
> From: Karl Berry
>
> I recently learned that some @menu vs. sectioning discrepancies in the
> automake manual were found with makeinfo 6.7, but not 7.1.
>
> In essence, I moved a subsection (Errors with distclean) from one
> section to another, but
> From: Gavin Smith
> Date: Tue, 12 Dec 2023 20:21:28 +
> Cc: bug-texinfo@gnu.org
>
> 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
> From: Gavin Smith
> Date: Sun, 3 Dec 2023 13:57:08 +
> Cc: bug-texinfo@gnu.org
>
> The solution that occurs to me is to recognise a third argument for
> @float. @float was introduced in Texinfo 4.7, in 2004. From NEWS:
>
> . new commands @float, @caption, @shortcaption, @listoffloats
> From: Bruno Haible
> Date: Tue, 14 Nov 2023 04:23:58 +0100
>
> Apparently some optimization options were still in effect. And indeed,
> the file tp/Texinfo/XS/config.status contains these lines:
>
> CC='sparc64-linux-gnu-gcc'
> compiler='sparc64-linux-gnu-gcc'
> LTCC='sparc64-linux-gnu-gcc'
>
> From: Bruno Haible
> Cc: bug-libunistr...@gnu.org
> Date: Sat, 11 Nov 2023 23:54:52 +0100
>
> [CCing bug-libunistring]
> Gavin Smith wrote:
> > I did not understand why uc_width was said to be "locale dependent":
> >
> > "These functions are locale dependent."
> >
> > - from
> >
> From: Gavin Smith
> Date: Fri, 10 Nov 2023 19:48:04 +
> Cc: Bruno Haible , bug-texinfo@gnu.org
>
> 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
> From: Gavin Smith
> Date: Thu, 9 Nov 2023 21:26:11 +
>
> I have just pushed a commit (e3a28cc9bf) to use gnulib/libunistring
> functions instead of the locale-dependent functions mbrtowc and wcwidth.
> This allows for a significant simplification as we do not have to try
> to switch to a
> Date: Mon, 6 Nov 2023 14:25:20 +0100
> From: pertu...@free.fr
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
>
> > Do these two replace the several *XS shared libraries we had until
> > Texinfo 7.1, or are they in addition to them?
>
> There are new *XS shared libraries in additions to
> Date: Mon, 6 Nov 2023 09:20:37 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , bug-texinfo@gnu.org
>
> On Sun, Nov 05, 2023 at 09:59:44PM +0200, Eli Zaretskii wrote:
> >
> > I don't have any libtexinfo shared library here, and I don't see one
> > being bu
> From: Gavin Smith
> Date: Sun, 5 Nov 2023 18:12:45 +
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
>
> So you know what a dynamically loaded library is; this contains a collection
> of functions and potentially data structures that can be loaded by running
> code and run as part of a
> From: Gavin Smith
> Date: Sun, 5 Nov 2023 17:04:47 +
>
> > Maybe one day libtexinfo could be a public library, but not for now
> > and libtexinfoxs should probably never ever be a public library.
>
> I agree neither of them should be a public library now.
Can someone please explain what
> From: Gavin Smith
> Date: Mon, 23 Oct 2023 19:52:49 +0100
> Cc: bug-texinfo@gnu.org
>
> I propose the following, more finished patch, which applies
> to Texinfo 7.1. We can also do something similar for the master branch.
Unfortunately, this change doesn't work on MS-Windows:
libtool:
> From: Gavin Smith
> Date: Sun, 22 Oct 2023 21:01:54 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 22, 2023 at 10:05:16PM +0300, Eli Zaretskii wrote:
> > > This patch, applied to 7.1, removes the recently added dTHX calls,
> > > but also removes the f
> From: Gavin Smith
> Date: Sun, 22 Oct 2023 19:35:11 +0100
> Cc: bug-texinfo@gnu.org
>
> One thing to try would to eliminate dTHX calls. If these are
> time-consuming on MinGW/MS-Windows, then extra calls will greatly slow
> down the program, due to the number of times the paragraph formatting
> From: Gavin Smith
> Date: Sun, 22 Oct 2023 18:41:34 +0100
> Cc: bug-texinfo@gnu.org
>
> > > Surprise: running with TEXINFO_XS=omit _reduces_ the elapsed time of
> > > producing the Emacs ELisp manual from 1:21.16 to 0:36.97.
> >
> > Another data point: running with TEXINFO_XS_PARSER=0 takes
> Date: Sun, 22 Oct 2023 17:30:15 +0300
> From: Eli Zaretskii
> Cc: bug-texinfo@gnu.org
>
> > From: Gavin Smith
> > Date: Sun, 22 Oct 2023 14:23:53 +0100
> > Cc: bug-texinfo@gnu.org
> >
> > > > First, check that the Perl extension modules are ac
> From: Gavin Smith
> Date: Sun, 22 Oct 2023 14:23:53 +0100
> Cc: bug-texinfo@gnu.org
>
> > > First, check that the Perl extension modules are actually being used. Try
> > > setting the TEXINFO_XS environment variable to "require" or "debug".
> >
> > I don't need to do that, I already verified
> From: Gavin Smith
> Date: Sun, 22 Oct 2023 13:35:19 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 22, 2023 at 12:06:21PM +0300, Eli Zaretskii wrote:
> > . makeinfo is painfully slow. For example, building the ELisp
> > manual that is part of Emac
> From: Gavin Smith
> Date: Wed, 18 Oct 2023 15:07:26 +0100
> Cc: bug-texinfo@gnu.org
>
> We have released version 7.1 of Texinfo, the GNU documentation format.
I'm sorry to say that makeinfo in this new release of Texinfo has
serious problems, when built with MinGW on MS-Windows. Here are the
> From: Gavin Smith
> Date: Thu, 19 Oct 2023 14:10:56 +0100
> Cc: bug-texinfo@gnu.org
>
> On Thu, Oct 19, 2023 at 03:26:51PM +0300, Eli Zaretskii wrote:
> > > diff --git a/info/info.c b/info/info.c
> > > index 8ca4a17e58..d7a6afaa2c 100644
> > >
> Date: Thu, 19 Oct 2023 08:20:49 -0400
> From: "Gavin D. Smith"
>
> +2023-10-19 Gavin Smith
> +
> + * info/info.c (get_initial_file),
> + * info/infodoc.c (info_get_info_help_node),
> + * info/nodes.c (info_get_node_with_defaults):
> + Use strcmp or strcasecmp instead of
> From: Bruno Haible
> Cc: bug-texinfo@gnu.org
> Date: Sun, 15 Oct 2023 16:07:28 +0200
>
> Eli Zaretskii wrote:
> > The stand-alone Info reader built with MinGW works
> > flawlessly for me.
> >
> > > I had understood that "info" w
> From: Bruno Haible
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Sun, 15 Oct 2023 16:25:56 +0200
>
> Eli Zaretskii wrote:
> > _popen accepts a MODE argument which can be used to control that, see
> >
> >
> > https://learn.microsoft.co
> From: Bruno Haible
> Cc: bug-texinfo@gnu.org
> Date: Sun, 15 Oct 2023 16:07:28 +0200
>
> Eli Zaretskii wrote:
> > The stand-alone Info reader built with MinGW works
> > flawlessly for me.
> >
> > > I had understood that "info" w
> From: Bruno Haible
> Date: Sun, 15 Oct 2023 15:23:45 +0200
>
> Gavin Smith wrote:
> > I had understood that "info" was running well on MinGW so it would be worth
> > understanding any differences between yours and Bruno's setup.
>
> I'm usually building with mingw-w64 5.0.3.
>
> Whereas Eli
> From: Bruno Haible
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Sun, 15 Oct 2023 15:11:33 +0200
>
> Eli Zaretskii wrote:
> > > For 'popen' and 'pclose', one needs the gnulib modules 'popen' and
> > > 'pclose',
> > > respectively.
>
> From: Gavin Smith
> Date: Sun, 15 Oct 2023 13:17:53 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 15, 2023 at 01:24:32PM +0200, Bruno Haible wrote:
> > - The behaviour of the 'ginfo' program on MSVC is the same as on mingw,
> > albeit not really useful currently: './info -f
> From: Gavin Smith
> Date: Sun, 15 Oct 2023 12:57:46 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 15, 2023 at 12:00:47PM +0300, Eli Zaretskii wrote:
> > Thanks.
> >
> > This doesn't compile with MinGW, because some of the dTHX additions I
> &g
> From: Bruno Haible
> Date: Sun, 15 Oct 2023 13:24:32 +0200
>
> For 'popen' and 'pclose', one needs the gnulib modules 'popen' and 'pclose',
> respectively.
Windows has _popen and _pclose, which can be used instead. That's
what MinGW does, AFAIK.
But I'm not sure Texinfo should try
> From: Gavin Smith
> Date: Sat, 14 Oct 2023 14:27:36 +0100
> Cc: platform-test...@gnu.org
>
> A pretest distribution for the next Texinfo release (7.1) has been
> uploaded to
>
> https://alpha.gnu.org/gnu/texinfo/texinfo-7.0.94.tar.xz
>
> There have not been many changes since the previous
> From: Gavin Smith
> Date: Sat, 14 Oct 2023 19:57:22 +0100
>
> It's all in the future, but I am slightly concerned about is duplicating
> in Texinfo existing system facilities. For example, for avoiding use of
> wcwidth, our use of which depends on setting a UTF-8 locale, and using
> the
> Date: Sat, 14 Oct 2023 11:57:02 +0200
> From: Patrice Dumas
> Cc: bug-texinfo@gnu.org
>
> On Thu, Oct 12, 2023 at 06:13:34PM +0300, Eli Zaretskii wrote:
> > What you say is not detailed enough, but using my crystal ball I think
> > you can have this with gl
> From: Gavin Smith
> Date: Fri, 13 Oct 2023 22:14:32 +0100
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
>
> 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
> Date: Fri, 13 Oct 2023 11:31:54 + (UTC)
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
> From: Werner LEMBERG
>
> >> [...] Neither collation corresponds to Unicode codepoints.
> >
> > That's exactly what we should not do.
>
> I strongly disagree.
>
> > People who read German don't
> Date: Fri, 13 Oct 2023 07:31:29 + (UTC)
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
> From: Werner LEMBERG
>
>
> >> OK, no tailoring. I wasn't aware of those differences, thanks for
> >> pointing me to it.
> >>
> >> Hopefully, we agree that `@documentlanguage` should set a
> >>
> Date: Fri, 13 Oct 2023 07:08:36 + (UTC)
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
> From: Werner LEMBERG
>
>
> >> ... there is probably a misunderstanding on my side. I don't know
> >> what you mean with 'tailoring', please give an example.
> >
> > This subject is too large and
> Date: Thu, 12 Oct 2023 20:30:47 + (UTC)
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
> From: Werner LEMBERG
>
> >> > I don't recommend to tailor index sorting for the language
> >> > indicated by @documentlanguage, either.
> >>
> >> This surprises me. Why not? For some languages, the
> Date: Thu, 12 Oct 2023 17:12:44 + (UTC)
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
> From: Werner LEMBERG
>
>
> > I don't recommend to tailor index sorting for the language indicated
> > by @documentlanguage, either.
>
> This surprises me. Why not? For some languages, the alphabetical
> Date: Thu, 12 Oct 2023 15:00:57 +0200
> From: Patrice Dumas
> Cc: bug-texinfo@gnu.org
>
> On Thu, Oct 12, 2023 at 01:29:27PM +0300, Eli Zaretskii wrote:
> > What is "smart sorting"? where is it described/documented?
>
> It is, in general, any way to
> Date: Thu, 12 Oct 2023 11:39:14 +0200
> From: Patrice Dumas
>
> One thing I could not find easily in C is something to replace the
> Unicode::Collate perl module for index entries sorting using 'smart'
> rules for sorting, that could be either found in Gnulib, included easily
> in the Texinfo
> From: Gavin Smith
> Date: Wed, 11 Oct 2023 18:15:04 +0100
> Cc: Patrice Dumas
>
> On Wed, Oct 11, 2023 at 06:12:51PM +0100, Gavin Smith wrote:
> > I will send you a diff to try to see if it lets the tests pass, or if
> > we need to make any further changes.
>
> Attached.
Thanks. This
> From: Gavin Smith
> Date: Tue, 10 Oct 2023 20:24:47 +0100
> Cc: br...@clisp.org, bug-texinfo@gnu.org
>
> On Tue, Oct 10, 2023 at 02:55:09PM +0300, Eli Zaretskii wrote:
> > > If this simple stub is preferable to the Gnulib implementation for
> > > MS-Windows,
> From: Gavin Smith
> Date: Tue, 10 Oct 2023 18:09:15 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Mon, Oct 09, 2023 at 11:32:49PM +0200, Bruno Haible wrote:
> > Gavin Smith wrote:
> > > It is supposed to attempt to force the locale to a UTF-8 local
> From: Gavin Smith
> Date: Mon, 9 Oct 2023 20:39:59 +0100
> Cc: Bruno Haible , bug-texinfo@gnu.org
>
> > IOW, unless the locale's codeset is UTF-8, any character that is not
> > printable _in_the_current_locale_ will return -1 from wcwidth. I'm
> > guessing that no one has ever tried to run
> Date: Mon, 9 Oct 2023 21:17:28 +0200
> From: Patrice Dumas
>
> On Sun, Oct 08, 2023 at 06:29:23PM +0100, Gavin Smith wrote:
> >
> > I remember that in the past, I broke up some of these lines to avoid
> > test failures on some platform that had different wcwidth results for
> > some
> From: Bruno Haible
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Mon, 09 Oct 2023 19:18:25 +0200
>
> Eli Zaretskii wrote:
> > > I just tried it now: On Linux (Ubuntu 22.04), in a de_DE.UTF-8 locale,
>
> Oops, typo: What I tested was the de_DE.ISO-88
> From: Bruno Haible
> Cc: bug-texinfo@gnu.org
> Date: Mon, 09 Oct 2023 18:15:05 +0200
>
> Eli Zaretskii wrote:
> > unless the locale's codeset is UTF-8, any character that is not
> > printable _in_the_current_locale_ will return -1 from wcwidth. I'm
> > gu
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 20:21:44 +0100
> Cc: bug-texinfo@gnu.org
>
> Just comparing the first line in the hunk:
>
> -(ì) @'{e} é (é) @'{@dotless{i}} í (í) @dotless{i} ı (ı) @dotless{j} ȷ
> +(ì) @'{e} é (é) @'{@dotless{i}} í (í) @dotless{i} ı (ı) @dotless{j} ȷ (ȷ)
>
> the
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 18:29:23 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 08, 2023 at 07:31:12PM +0300, Eli Zaretskii wrote:
> > I see a very large diff, full of non-ASCII characters. A typical hunk
> > is below:
> >
> >
> Date: Sun, 08 Oct 2023 19:31:12 +0300
> From: Eli Zaretskii
> Cc: bug-texinfo@gnu.org
>
> I see a very large diff, full of non-ASCII characters. A typical hunk
> is below:
>
> -(ì) @'{e} é (é) @'{@dotless{i}} í (í) @dotless{i} ı (ı) @dotless{j} ȷ
> -(ȷ) ‘@H{
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 17:04:36 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 08, 2023 at 04:55:24PM +0300, Eli Zaretskii wrote:
> > > Date: Sun, 08 Oct 2023 16:42:05 +0300
> > > From: Eli Zaretskii
> > > CC: bug-texinfo@gnu
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 16:33:22 +0100
> Cc: bug-texinfo@gnu.org
>
> > > Hence, I propose to initialise n to 0, rather than 120 as in the patch
> > > below.
> >
> > No, the value must be positive, otherwise it still crashes. It's a
> > bug in MinGW implementation.
>
> Can
> Date: Sun, 08 Oct 2023 16:42:05 +0300
> From: Eli Zaretskii
> CC: bug-texinfo@gnu.org
>
> The next set of problems is in install-info: the new code in this
> version fails to close files, and then Windows doesn't let us
> remove/rename them. The result is that almost
> Date: Sun, 08 Oct 2023 14:39:36 +0300
> From: Eli Zaretskii
> CC: bug-texinfo@gnu.org
>
> Sorry, I was mistaken: the Gnulib getdelim is not used here. Instead,
> this build uses the MinGW implementation of getdelim, and that one has
> a subtle bug, which rears its ugly he
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 12:50:51 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 08, 2023 at 02:39:36PM +0300, Eli Zaretskii wrote:
> > Sorry, I was mistaken: the Gnulib getdelim is not used here. Instead,
> > this build uses the MinGW
> Date: Sun, 08 Oct 2023 12:41:19 +0300
> From: Eli Zaretskii
> Cc: bug-texinfo@gnu.org
>
> Starting program: d:\usr\Perl\bin\perl.exe ../tp/texi2any.pl info-stnd.texi
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x692a6fc6 in getdelim ()
> fr
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 08:50:51 +0100
> Cc: bug-texinfo@gnu.org
>
> The program appears to crash after the "@include version-stnd.texi" line
> which read a new input file. This suggests that the problem may be to
> do with reading input, somewhere in 'next_text' in input.c.
> From: Gavin Smith
> Date: Sat, 7 Oct 2023 17:26:51 +0100
> Cc: bug-texinfo@gnu.org
>
> I've changed xspara__print_escaped_spaces not to use malloc and free,
> although adding dTHX should be harmless.
Yes, I've seen that. Applying that change doesn't prevent the
crashes.
> Try going into the
> From: Gavin Smith
> Date: Sat, 30 Sep 2023 17:16:57 +0100
> Cc: platform-test...@gnu.org
>
> A pretest distribution for the next Texinfo release (7.1) has been
> uploaded to
>
> https://alpha.gnu.org/gnu/texinfo/texinfo-7.0.93.tar.xz
This fails to build on MS-Windows with mingw.org's MinGW.
> From: Gavin Smith
> Date: Wed, 6 Sep 2023 02:51:47 +0100
>
> On Tue, Sep 05, 2023 at 09:16:47PM +0200, Patrice Dumas wrote:
> > I think I understand what you don't understand, actually this is not
> > about displaying the characters, which is not really done by texi2any,
> > it is about
> Date: Tue, 5 Sep 2023 21:16:47 +0200
> From: Patrice Dumas
> Cc: bug-texinfo@gnu.org
>
> I think I understand what you don't understand, actually this is not
> about displaying the characters, which is not really done by texi2any,
> it is about situations where we need to count the width of
> Date: Tue, 5 Sep 2023 20:19:40 +0200
> From: Patrice Dumas
> Cc: bug-texinfo@gnu.org
>
> On Tue, Sep 05, 2023 at 09:09:18PM +0300, Eli Zaretskii wrote:
> > > Date: Tue, 5 Sep 2023 20:01:53 +0200
> > > From: Patrice Dumas
> > >
> > > Curren
> Date: Tue, 5 Sep 2023 20:01:53 +0200
> From: Patrice Dumas
>
> Currently, when counting the width of a line of character, we count
> control characters that are also spaces as having a width of 1. I think
> that it is not good, as control characters either should not have a
> width, for end
> From: Gavin Smith
> Date: Fri, 18 Aug 2023 14:47:48 +0100
> Cc: bug-texinfo@gnu.org
>
> As the log file shows, the Unicode::Collate module is not found. I don't
> know what the solution to this is.
>
> It is meant to be included (in the "perl core") with perl 5.26.3 (the perl
> version
> From: Bruno Haible
> Date: Fri, 18 Aug 2023 01:00:01 +0200
>
> On mingw 5.0.3, I see 56 test failures:
>
> FAIL: ii-0001-test
> FAIL: ii-0002-test
Isn't this a problem with different EOL conventions in the expected
results and in what install-info compiled for Windows produces? If
so, you
> Date: Mon, 5 Jun 2023 08:11:00 -0700
> From: Raymond Toy
>
> It appears not to be consistent. We have this in the texinfo source:
>
>
> @fnindex N'th previous output
>
> with a real apostrohpe. The info file has
>
>
> * N'th previous output: Functions and Variables for
> Date: Mon, 5 Jun 2023 07:18:00 -0700
> From: Raymond Toy
>
> Maxima grovels over the html file to find appropriate links to use for the
> html version of the manual.
> This was working fine with 6.8 and earlier because I found appropriate
> regexps to find the links.
>
> This stopped
[Please keep the list address on the CC.]
> From: Sebastian Carlos
> Date: Fri, 21 Apr 2023 17:30:20 +0200
>
> Stand-alone GNU Info for version 7.0.3, where I only found two mentions:
>
> > --all, -a
> > Find all files matching manual. Three usage patterns are supported, as
> > follows.
> >
> From: Sebastian Carlos
> Date: Fri, 21 Apr 2023 16:51:30 +0200
>
> I noticed that GNU Info does render man pages, but there's no mention of this
> feature on the GNU Info
> manual. And it's not entirely clear if there's a way to explicitly read man
> pages with GNU Info, or if it's
> just a
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 20:13:32 +0200
>
> Eli Zaretskii writes:
>
> > Btw, I just built Texinfo 7.0.3, and info.exe still displays Unicode
> > quotes as I expect: transliterate
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 14:18:50 +0200
>
> Eli Zaretskii writes:
>
> > Why on Earth is a system header included only in msys2-runtime-devel?
> >
> > Also, is msys2-runtime-devel ab
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 13:22:46 +0200
>
> Eli Zaretskii writes:
>
> > The only Windows-specific issue I'm aware of is that the 'configure'
> > command should point to the
> From: Arash Esbati
> Cc: bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 08:55:22 +0200
>
> I see that Texinfo doesn't have any instructions how to build and install
> Texinfo with MinGW64. Should I make a proposal?
It depends on what MinGW64-specific nits you think should be there.
The only
> From: Gavin Smith
> Date: Wed, 5 Apr 2023 14:59:23 +0100
> Cc: pertu...@free.fr, ar...@gnu.org, bug-texinfo@gnu.org
>
> Might it be better to round-trip through intptr_t rather than through
> a pointer type?
Yes, I think this will be better. Cleaner, too.
> > I think you are forgetting the
> From: Gavin Smith
> Date: Wed, 5 Apr 2023 12:24:58 +0100
> Cc: Patrice Dumas , ar...@gnu.org, bug-texinfo@gnu.org
>
> GNU coding standards (Info node (standards)CPU Portability):
>
> You need not cater to the possibility that 'long' will be smaller
> than pointers and 'size_t'. We
> Date: Wed, 5 Apr 2023 11:31:12 +0200
> From: Patrice Dumas
> Cc: Arash Esbati , bug-texinfo@gnu.org
>
> On Wed, Apr 05, 2023 at 11:47:08AM +0300, Eli Zaretskii wrote:
> > Those are real bugs: we should cast to inptr_t instead of long.
>
> We already do that in s
> From: Arash Esbati
> Date: Wed, 05 Apr 2023 09:46:28 +0200
>
> The only other warnings I get are (linebreaks added manually):
>
> --8<---cut here---start->8---
> parsetexi/handle_commands.c: In function 'handle_other_command':
>
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Tue, 04 Apr 2023 15:32:47 +0200
>
> Sure. And just to confirm: I opened a cmd.exe, adjusted %path% so I
> have the mingw64 directories for its .dll's included, adjusted
> %infopath% and did
>
>
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Tue, 04 Apr 2023 15:05:01 +0200
>
> >> C:\>chcp
> >> Aktive Codepage: 850.
> >
> > That's likely the problem: this codepage doesn't support Unicode
> > quotes. What remains to be understood is why doesn't
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 13:56:23 +0100
> Cc: ar...@gnu.org, bug-texinfo@gnu.org
>
> Ok, so assuming that this is all correct, we know that it is possible
> to build Texinfo for MSYS2 because it was done officially, and Arash
> had the official MSYS2 info program installed.
>
> Date: Tue, 04 Apr 2023 15:11:01 +0300
> From: Eli Zaretskii
> Cc: ar...@gnu.org, bug-texinfo@gnu.org
>
> There's an easier way:
>
> (gdb) ./ginfo.exe
Sorry, this was supposed to be
$ gdb ./ginfo.exe
> Date: Tue, 4 Apr 2023 12:48:14 +0200
> From: Patrice Dumas
>
> On Tue, Apr 04, 2023 at 10:59:53AM +0100, Gavin Smith wrote:
> > On Tue, Apr 04, 2023 at 09:35:07AM +0200, Arash Esbati wrote:
> > > Eli Zaretskii writes:
> > >
> > > &
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 10:59:53 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Tue, Apr 04, 2023 at 09:35:07AM +0200, Arash Esbati wrote:
> > Eli Zaretskii writes:
> >
> > > ??? What is your console output codepage set to?
>
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 10:56:28 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> The other thing that I am confused about is that you said you were
> building on "Win10, Msys2/MinGW64". Would Msys2 and MinGW64 not
> be tw
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 10:34:23 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Tue, Apr 04, 2023 at 09:35:07AM +0200, Arash Esbati wrote:
> > Eli Zaretskii writes:
> >
> > > What do you get from rpl_nl_lan
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Tue, 04 Apr 2023 09:35:07 +0200
>
> > ??? What is your console output codepage set to?
>
> C:\>chcp
> Aktive Codepage: 850.
That's likely the problem: this codepage doesn't support Unicode
quotes. What
> Date: Mon, 03 Apr 2023 19:43:54 +0300
> From: Eli Zaretskii
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
>
> > and Msys2 info looks like this:
>
> Your MSYS2 Info was built without libiconv, right?
Actually, that's not it: MSYS2 build is not a MinGW build at a
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Mon, 03 Apr 2023 18:32:13 +0200
>
> > What happens if you invoke 'info' from the default Windows Command
> > Prompt window? does the problem persist?
>
> My build looks like this in cmd.exe:
??? What is your
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Mon, 03 Apr 2023 18:11:13 +0200
>
> Eli Zaretskii writes:
>
> > Which console is this? Is this a Command Prompt window, or some kind
> > of MSYS2 terminal emulator (mintty)?
>
1 - 100 of 1040 matches
Mail list logo
