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
> can commit before or after changing the perl parser for this change,
> actually.
Thanks
Gavin Smith writes:
> I have just tried this and it works fine, so it must be something Msys2
> specific.
I thought so.
> It is probably related to the use of backslash as a directory path
> separator. I tested a node name with a forward slash and this had the
> same problem:
>
> $ info '(texi
On Sun, Jan 22, 2023 at 01:05:26PM +0100, Arash Esbati wrote:
> Hi all,
>
> I'm observing an issue where backslashes and possibly & signs in node
> names don't work. The following calls of node names work:
>
> info '(latex2e)Overview'
> info '(latex2e)Document classes'
>
> But this one brea
We have released version 7.0.2 of Texinfo, the GNU documentation format.
This is a minor bug-fix release containing minimal changes from the
previous release (7.0.1).
This package contains tools to produce documentation in various
formats, including HTML and PDF, from source files in the Texinfo
Hi all,
I'm observing an issue where backslashes and possibly & signs in node
names don't work. The following calls of node names work:
info '(latex2e)Overview'
info '(latex2e)Document classes'
But this one breaks:
info '(latex2e)\indent & \noindent'
=> info: ./(latex2e)\indent & \noin
On Sun, Jan 22, 2023 at 06:57:22AM +, Sam James wrote:
>
>
> > On 21 Jan 2023, at 21:35, jake roggenbuck wrote:
> >
> > To whom it may concern,
> >
> > I have found a crash and segfault in texinfo (info).
> >
> > Here is how you reproduce the segfault.
> >
> > ```
> > cat /dev/urandom |
