Hi Gavin,
Gavin Smith writes:
> This can be configured using the scroll-behaviour and cursor-motion-scrolls
> variables in .infokey (see Info node (info-stnd)Variables).
>
> The info-stnd manual starts,
>
> You can read through the rest of this manual by typing and
> (or and )
>
> I doubt
On Sat, Dec 10, 2022 at 03:11:48PM +, 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
Hi
I install the latest version of texinfo (texinfo-7.0.1) and found this
warning:
gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../gnulib/lib -I../gnulib/lib
-DLOCALEDIR=\"/usr/local/share/locale\" -g -O2 -MT install-info.o -MD -MP
-MF .deps/install-info.Tpo -c -o install-info.o install-info.c
In file
On Sat, Jan 07, 2023 at 05:10:39PM +0200, Eli Zaretskii wrote:
>
> How do you see that there's "a file with the two nodes concatenated".
> What I see is index.html and Node1.html. The contents of the latter
> is this:
Well, the first Node1.html that was generated had both nodes
concatenated, but
> Date: Sat, 7 Jan 2023 15:41:36 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , torbjorn.svens...@foss.st.com,
> bug-texinfo@gnu.org
>
> On Sat, Jan 07, 2023 at 03:37:21PM +0200, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Sat, 7 Jan 2023 12:29:33 +
> > > Cc: pertu...@f
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 Wed, Jan 04, 2023 at 07:44:58PM +, Gavin Smith wrote:
> > These added directories res_latex look wrong. Theses tests are in
> > @test_formatted, and the latex test is 'latex' which should only lead to
> > content in the .pl file, like t/results/indices/empty_index_entry.pl.
> > (There shoul
On Sat, Jan 07, 2023 at 03:37:21PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sat, 7 Jan 2023 12:29:33 +
> > Cc: pertu...@free.fr, torbjorn.svens...@foss.st.com, bug-texinfo@gnu.org
> >
> > On Sat, Jan 07, 2023 at 01:06:41PM +0200, Eli Zaretskii wrote:
> > > How do you "set"
> From: Gavin Smith
> Date: Sat, 7 Jan 2023 12:29:33 +
> Cc: pertu...@free.fr, torbjorn.svens...@foss.st.com, bug-texinfo@gnu.org
>
> On Sat, Jan 07, 2023 at 01:06:41PM +0200, Eli Zaretskii wrote:
> > How do you "set" the CASE_INSENSITIVE_FILENAMES from the command line?
> > It looks like the
On Sat, Jan 07, 2023 at 01:06:41PM +0200, Eli Zaretskii wrote:
> AFAIR, makeinfo 4.x avoided the problem completely by _always_
> behaving as if the filesystem were case-insensitive. It produced a
> single file for all the nodes whose names clashed, and used the node
> name in the cross-references
On Sat, Jan 07, 2023 at 11:28:45AM +0100, Torbjorn SVENSSON wrote:
> I don't think that texi2any should try to be smart and poke the file system
> as the file system that the makeinfo command happens to put the output on
> might not be the final file system and it can have very different
> properti
On Sat, Jan 07, 2023 at 01:06:41PM +0200, Eli Zaretskii wrote:
> How do you "set" the CASE_INSENSITIVE_FILENAMES from the command line?
> It looks like the Texinfo manual says VAR=VALUE, but what VALUE should
> be used in this case? And what will that do in terms of the output
> produced for the s
> Date: Sat, 7 Jan 2023 11:21:29 +0100
> From: pertu...@free.fr
> Cc: gavinsmith0...@gmail.com, torbjorn.svens...@foss.st.com,
> bug-texinfo@gnu.org
>
> On Sat, Jan 07, 2023 at 11:54:03AM +0200, Eli Zaretskii wrote:
> > > Date: Sat, 7 Jan 2023 10:38:57 +0100
> > > From: pertu...@free.fr
> >
On 2023-01-07 11:09, Patrice Dumas wrote:
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
On 2023-01-07 11:21, pertu...@free.fr wrote:
On Sat, Jan 07, 2023 at 11:54:03AM +0200, Eli Zaretskii wrote:
Date: Sat, 7 Jan 2023 10:38:57 +0100
From: pertu...@free.fr
Cc: Gavin Smith , torbjorn.svens...@foss.st.com,
bug-texinfo@gnu.org
No, what I would like to know is whether nodes
On Sat, Jan 07, 2023 at 11:54:03AM +0200, Eli Zaretskii wrote:
> > Date: Sat, 7 Jan 2023 10:38:57 +0100
> > From: pertu...@free.fr
> > Cc: Gavin Smith , torbjorn.svens...@foss.st.com,
> > bug-texinfo@gnu.org
> >
> > No, what I would like to know is whether nodes are concatenated when
> > split
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
> Date: Sat, 7 Jan 2023 10:38:57 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , torbjorn.svens...@foss.st.com,
> bug-texinfo@gnu.org
>
> No, what I would like to know is whether nodes are concatenated when
> split, or there is only one node in the output.
Only one node is in the output,
On Sat, Jan 07, 2023 at 09:08:56AM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sat, 7 Jan 2023 00:35:25 +
> >
> > > Does anybody knows if nodes are correctly concatenated with case
> > > insensitive filesystems if CASE_INSENSITIVE_FILENAMES is not set?
> >
> > It would be goo
On 2023-01-06 22:52, 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 patches, so pardon me if this is the wrong
channel.
It is the right channel.
I recentl
20 matches
Mail list logo
