> On 8 Nov 2022, at 16:34, Gavin Smith wrote:
>
> I thought we could discuss whether we should use any kind of git branch
> structure for the development of Texinfo. A related question is whether
> we should do minor releases for bug fixes and translation updates. For
> example, shortly after
On Tue, Nov 8, 2022 at 2:02 PM 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, I have
On 2022-11-08 16:42:00 +, Gavin Smith wrote:
> On Tue, Nov 08, 2022 at 11:27:08AM +0100, Vincent Lefevre wrote:
> > On 2022-11-08 07:04:11 +, Gavin Smith wrote:
> > > On Tue, Nov 08, 2022 at 03:57:48AM +0100, Vincent Lefevre wrote:
> > > > Note that there is the same issue with a Texinfo ma
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, I have 1.16.2, but I haven't
tried building texinfo there yet.
--
Ray
On Tue, Nov 08, 2022 at 09:48:31PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Tue, 8 Nov 2022 19:34:51 +
> > Cc: bug-texinfo@gnu.org
> >
> > When we did a new major release, would we merge "master" into "release"?
>
> No, you just cut a new release branch. The release branc
> From: Gavin Smith
> Date: Tue, 8 Nov 2022 19:34:51 +
> Cc: bug-texinfo@gnu.org
>
> When we did a new major release, would we merge "master" into "release"?
No, you just cut a new release branch. The release branch is only for
a certain release or a series of releases, depending on the
dev
On Tue, Nov 08, 2022 at 07:07:49PM +0200, Eli Zaretskii wrote:
> > What kind of structure should we use to apply fixes to both the main
> > line of development and to the release branch?
>
> There are basically 2 workflows:
>
> . fixes for the release branch are committed to that branch, and th
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 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 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 Dumas
>
>
On Tue, Nov 08, 2022 at 11:30:30AM +, Werner LEMBERG wrote:
>
> [texinfo 7.0]
> [perl 5.26.1]
>
>
> Two issues.
>
> * Running
>
> ```
> LANGUAGE=de LANG=en_US.utf8 makeinfo
> ```
>
> on the command line gives the warning message
>
> ```
> Wide character in die at /usr/local/b
> From: Gavin Smith
> Date: Tue, 8 Nov 2022 16:34:03 +
>
> We have always developed Texinfo in a linear fashion (in git and before
> that SVN). However, the development repository is not necessarily always
> in a fit state to be released with new work being done. So one question
> I have is
On Tue, Nov 08, 2022 at 11:30:30AM +, Werner LEMBERG wrote:
>
> * Unpack the attached tarball and execute
>
> ```
> LANG=C makeinfo changes.texi
> ```
>
> It aborts with
>
> ```
> Can't use an undefined value as an ARRAY reference at
> /usr/local/share/texinfo/Texinfo/Convert
On Tue, Nov 08, 2022 at 11:27:08AM +0100, Vincent Lefevre wrote:
> On 2022-11-08 07:04:11 +, Gavin Smith wrote:
> > On Tue, Nov 08, 2022 at 03:57:48AM +0100, Vincent Lefevre wrote:
> > > Note that there is the same issue with a Texinfo macro, i.e. with
> > >
> > > @iftex
> > > @macro atan
> >
On Tue, Nov 08, 2022 at 08:22:03AM -0800, Raymond Toy wrote:
> I did a git clone of texinfo, changed to the texinfo-7.0 branch and tried
> to build it. It didn't work.
>
> I ran autogen.sh and got the message:
>
> Preparing Texinfo development infrastructure:
> ./tp/maintain/regenerate_file_li
I thought we could discuss whether we should use any kind of git branch
structure for the development of Texinfo. A related question is whether
we should do minor releases for bug fixes and translation updates. For
example, shortly after Texinfo 6.8 was released (in July 2021), glibc 2.34
was rel
I did a git clone of texinfo, changed to the texinfo-7.0 branch and tried
to build it. It didn't work.
I ran autogen.sh and got the message:
Preparing Texinfo development infrastructure:
./tp/maintain/regenerate_file_lists.pl
(cd tp && ./maintain/regenerate_docstr.sh Makefile.docstr)
(cd t
On Tue, Nov 8, 2022 at 8:04 AM Patrice Dumas wrote:
> 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
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 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 bottom navbar is missing. I
noticed this first at
https://cmucl.org/docs/
[texinfo 7.0]
[perl 5.26.1]
Two issues.
* Running
```
LANGUAGE=de LANG=en_US.utf8 makeinfo
```
on the command line gives the warning message
```
Wide character in die at /usr/local/bin/makeinfo line 1332.
```
* Unpack the attached tarball and execute
```
LANG=C makeinfo
On 2022-11-08 07:04:11 +, Gavin Smith wrote:
> On Tue, Nov 08, 2022 at 03:57:48AM +0100, Vincent Lefevre wrote:
> > Note that there is the same issue with a Texinfo macro, i.e. with
> >
> > @iftex
> > @macro atan
> > \\mathop{\\rm atan}
> > @end macro
> > @end iftex
> >
> > instead of the \gd
22 matches
Mail list logo
