> From: Gavin Smith
> Date: Tue, 10 Sep 2024 16:32:26 +0100
> Cc: help-texinfo@gnu.org
>
> > I was able to install a working version of texinfo from gnuwin32, but it
> > seems to lack texi2any. I was able to run makeinfo --html, but while it
> > runs, gives me lots of errors (along the lines of "
> From: Gavin Smith
> Date: Tue, 10 Sep 2024 16:29:43 +0100
> Cc: help-texinfo@gnu.org
>
> On Tue, Sep 10, 2024 at 07:00:15PM +0530, Biswapriyo Nath wrote:
> > I am trying to compile texinfo 7.1.1 with gcc 14 mingw toolchain and
> > got the following compiler error.
> >
> > pcterm.c: In function
> From: Benjamin Kalish
> Date: Tue, 10 Sep 2024 10:20:07 -0400
>
> Any advice on how to get a working instance of texi2any on Windows would be
> most welcome. I began a project
> on my Mac at home, but when I got to work, where we use only Windows
> computers, I was unable to find a
> texinfo
> Date: Sun, 17 Mar 2024 12:29:01 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , ar...@aarsen.me,
> help-texinfo@gnu.org
>
> On Sat, Mar 16, 2024 at 09:29:59AM +0200, Eli Zaretskii wrote:
> > If and when we understand the rationale for that code, and you can
&g
> Date: Sat, 16 Mar 2024 16:13:35 +0100
> From: pertu...@free.fr
> Cc: gavinsmith0...@gmail.com, ar...@aarsen.me, help-texinfo@gnu.org
>
> On Sat, Mar 16, 2024 at 04:49:11PM +0200, Eli Zaretskii wrote:
> > > Here are my interrogations. First I have three questions about r
> Date: Sat, 16 Mar 2024 15:13:04 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , ar...@aarsen.me,
> help-texinfo@gnu.org
>
> On Sat, Mar 16, 2024 at 09:29:59AM +0200, Eli Zaretskii wrote:
> > > For example, I looked at the mentioned code at
> > &g
> Date: Sat, 16 Mar 2024 00:12:21 +0100
> From: Patrice Dumas
> Cc: gavinsmith0...@gmail.com, ar...@aarsen.me, help-texinfo@gnu.org
>
> On Fri, Mar 15, 2024 at 09:42:28AM +0200, Eli Zaretskii wrote:
> >
> > I think the main reason this solution is not used is tha
> From: Gavin Smith
> Date: Fri, 15 Mar 2024 21:22:17 +
> Cc: Patrice Dumas , ar...@aarsen.me, help-texinfo@gnu.org
>
> For example, I looked at the mentioned code at
> https://git.savannah.gnu.org/cgit/emacs.git/tree/admin/admin.el
> (the manual-html-fix-* functions) and it is not instantly
> Date: Thu, 14 Mar 2024 22:52:20 +0100
> From: Patrice Dumas
> Cc: Gavin Smith , ar...@aarsen.me,
> help-texinfo@gnu.org
>
> I had a look at the code in admin/admin.el that (unless I missed
> something) seems to do that, and indeed, it makes extensive changes and
> needs to parse specific
> From: Arsen Arsenović
> Cc: Eli Zaretskii , help-texinfo@gnu.org
> Date: Thu, 14 Mar 2024 22:34:00 +0100
>
> >> Ha! the amount of grief those changes caused the Emacs maintainers is
> >> beyond complaining. We have a script that massages the produced HTML
>
> From: Gavin Smith
> Date: Wed, 13 Mar 2024 17:30:53 +
> Cc: Eli Zaretskii , help-texinfo@gnu.org
>
> > > Changing such long-standing behavior just because it looks like
> > > "redundant" is not the best idea IME, but if no manuals and no
> >
> From: Gavin Smith
> Date: Tue, 12 Mar 2024 17:31:36 +
> Cc: "help-texinfo@gnu.org"
>
> On Tue, Mar 12, 2024 at 01:14:19PM +0100, Arsen Arsenović wrote:
> > Hello,
> >
> > Currently, makeinfo generates HTML elements that contain a node
> > name. This is good. However, for the top node,
> From: Gavin Smith
> Date: Mon, 12 Feb 2024 17:24:30 +
> Cc: ralphli...@hotmail.com, help-texinfo@gnu.org
>
> > > Inside screen.texi, which is included by emacs.texi before commands.texi,
> > > there appears to be an unterminated footnote:
> > >
> > > 所选窗口中的光标显示大多数编辑命令生效的位置，称为 @dfn{光标}@fo
> From: Gavin Smith
> Date: Mon, 12 Feb 2024 16:03:19 +
> Cc: help-texinfo@gnu.org
>
> I started by simply running "xetex emacs.texi" in the files you sent me.
> I had an error message about nested footnotes:
>
> (./commands.texi 章 2
> ! Nested footnotes not supported in texinfo.tex, even th
> Date: Sat, 20 Jan 2024 19:01:25 +0100
> From: Patrice Dumas
> Cc: emacs-de...@gnu.org, help-texinfo@gnu.org
>
> Not necessarily very important, but UTF-8 is the default input encoding
> since Texinfo 6.7 (23 September 2019), depending on the Texinfo minimal
> version you target, you could remov
> Date: Fri, 19 Jan 2024 18:00:34 +
> From: Jean-Christophe Helary
> Cc: help-texinfo@gnu.org
>
> I’m trying here to make a summary of the discussions that we’ve had so far,
> in the hope of being able to propose a proper readme file at some point in
> the close future.
>
> I hope I've not
> From: Daniel Cerqueira
> Cc: Patrice Dumas , Eli Zaretskii ,
> jean.christophe.hel...@traductaire-libre.org, stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
> Date: Fri, 12 Jan 2024 14:42:58 +
>
> From: Vincent Belaïche
> CC: "pertu...@free.fr" ,
> "jean.christophe.hel...@traductaire-libre.org"
> , "stefankan...@gmail.com"
> , "emacs-de...@gnu.org" ,
> "r...@gnu.org" , "help-texinfo@gnu.org"
>
> Date: Thu, 11 Jan 2024 21:58:20 +
>
> Emacs info viewer inserts
> From: Gavin Smith
> Date: Thu, 11 Jan 2024 19:46:30 +
> Cc: pertu...@free.fr, jean.christophe.hel...@traductaire-libre.org,
> stefankan...@gmail.com, vincent@hotmail.fr, emacs-de...@gnu.org,
> r...@gnu.org, help-texinfo@gnu.org
>
> > > Although it's not ideal, using cross-re
> From: Daniel Cerqueira
> Cc: Daniel Cerqueira , pertu...@free.fr,
> jean.christophe.hel...@traductaire-libre.org, stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
> Date: Thu, 11 Jan 2024 19:14:36 +
>
> Sorry Eli, I did le
n 11, 2024 at 06:09:20PM +0200, Eli Zaretskii wrote:
> > > The node name may be visible in the output, so if English node names are
> > > used they won't be in the translated manual language. So I do not think
> > > that is it correct, in general, to use the English n
> Date: Thu, 11 Jan 2024 16:56:15 +0100
> From: Patrice Dumas
> Cc: jean.christophe.hel...@traductaire-libre.org, stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> > Having @anchor with the English node name will allow cros
> Date: Thu, 11 Jan 2024 14:49:12 +0100
> From: Patrice Dumas
> Cc: jean.christophe.hel...@traductaire-libre.org, stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> > The translator doesn't always know whether a translated m
> From: Daniel Cerqueira
> Cc: Patrice Dumas ,
> jean.christophe.hel...@traductaire-libre.org, stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
> Date: Thu, 11 Jan 2024 12:48:46 +
>
> > The translator doesn't always know whet
> Date: Wed, 10 Jan 2024 21:52:23 +0100
> From: Patrice Dumas
> Cc: Eli Zaretskii , Stefan Kangas ,
> Vincent Belaïche ,
> emacs-de...@gnu.org, r...@gnu.org, help-texinfo@gnu.org
>
> In any case, if a target manual is not yet translated, to me it is the
&g
> Date: Sun, 07 Jan 2024 05:38:51 +
> From: Jean-Christophe Helary
> Cc: Eli Zaretskii , stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> >> Do you mean that a translated manual should have an @anchor
> From: Gavin Smith
> Date: Sat, 6 Jan 2024 21:17:35 +
> Cc: jean.christophe.hel...@traductaire-libre.org, stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> On Sat, Jan 06, 2024 at 10:41:11PM +0200
> From: Gavin Smith
> Date: Sat, 6 Jan 2024 20:16:54 +
> Cc: jean.christophe.hel...@traductaire-libre.org, stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> > > If desired, users could have a directory containing solely
> From: Gavin Smith
> Date: Sat, 6 Jan 2024 20:02:32 +
> Cc: Eli Zaretskii ,
> Jean-Christophe Helary ,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> > I'd probably take it a step further and
> From: Gavin Smith
> Date: Sat, 6 Jan 2024 19:41:27 +
> Cc: Eli Zaretskii , stefankan...@gmail.com,
> vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> On Sat, Jan 06, 2024 at 01:49:53PM +, Jean-Christophe Helary wrote:
>
> From: Gavin Smith
> Date: Sat, 6 Jan 2024 19:03:33 +
> Cc: Eli Zaretskii , Stefan Kangas ,
> Vincent Belaïche ,
> emacs-de...@gnu.org, Richard Stallman ,
> help-texinfo@gnu.org
>
> It's up to people writing the Texinfo manuals what the
> Date: Sat, 06 Jan 2024 14:16:23 +
> From: Jean-Christophe Helary
> Cc: Stefan Kangas , Vincent Belaïche
> , emacs-de...@gnu.org, Richard Stallman
> , help-texinfo@gnu.org
>
> > I think we'd need something more complex there. One possibility could
> > be some kind of "translation table"
> Date: Sat, 06 Jan 2024 13:49:53 +
> From: Jean-Christophe Helary
> Cc: stefankan...@gmail.com, vincent@hotmail.fr, emacs-de...@gnu.org,
> r...@gnu.org, help-texinfo@gnu.org
>
> Thinking out loud here, but @node currently requires the node-name
> argument and has next/preious/up option
> Date: Sat, 06 Jan 2024 12:25:55 +
> From: Jean-Christophe Helary
> Cc: Stefan Kangas , Vincent Belaïche
> , emacs-de...@gnu.org, Richard Stallman
> , help-texinfo@gnu.org
>
> > On Jan 6, 2024, at 20:38, Eli Zaretskii wrote:
> >
> >> 1. I read a ma
> From: Stefan Kangas
> Date: Sat, 6 Jan 2024 03:57:24 -0800
> Cc: vincent@hotmail.fr, emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> Eli Zaretskii writes:
>
> >> If that’s the case, what about using “Translated manuals” for now,
>
> Date: Sat, 06 Jan 2024 09:37:03 +
> From: Jean-Christophe Helary
> Cc: Stefan Kangas , Vincent Belaïche
> , emacs-de...@gnu.org, r...@gnu.org,
> help-texinfo@gnu.org
>
> >> Would @author be also used for the translator?
> >
> > @author is a TeX command and goes into the printed version.
> Date: Sat, 06 Jan 2024 04:40:41 +
> From: Jean-Christophe Helary
> Cc: Stefan Kangas , Vincent Belaïche
> , emacs-de...@gnu.org, Richard Stallman
> , help-texinfo@gnu.org
>
> > I wasn't talking about the manuals. But even for the manuals there
> > are some issues that need to be consider
> From: Gavin Smith
> Date: Sun, 31 Dec 2023 12:32:21 +
> Cc: dan.l...@brilhante.top, pertu...@free.fr, help-texinfo@gnu.org
>
> On Sun, Dec 31, 2023 at 08:52:20AM +0200, Eli Zaretskii wrote:
> > Btw, what exactly does makeinfo produce for cross-references when
> &g
> Date: Sun, 31 Dec 2023 08:38:34 +0200
> From: Eli Zaretskii
> Cc: gavinsmith0...@gmail.com, pertu...@free.fr, help-texinfo@gnu.org
>
> > From: Daniel Cerqueira
> > Cc: Patrice Dumas , Daniel Cerqueira
> > , help-texinfo@gnu.org
> > Date: Sat, 30 Dec 2023
> From: Daniel Cerqueira
> Cc: Patrice Dumas , Daniel Cerqueira
> , help-texinfo@gnu.org
> Date: Sat, 30 Dec 2023 21:00:24 +
>
> I hate when programs try to be smart, like Emacs was trying to be.
> Because, then I need to bother people with specialized knowleadge, when
> this thing should
> From: Gavin Smith
> Date: Tue, 14 Nov 2023 21:58:01 +
>
> @anchor should not appear in any context where it does not
> correspond to a single position in the output file.
Good luck with documenting this restriction in a way that Texinfo
users can use in practice without a very deep underst
> From: Rob Krum
> Date: Sat, 29 Jul 2023 20:31:27 -0700
> Cc: Vitezslav Crhonek , help-texinfo@gnu.org
>
> Though I think the modification date will throw people off, but I sincerely
> doubt we could find an
> original, concrete date.
The original release data of Texinfo 4.2 was 1 Apr 2002.
> From: Dirk Gouders
> Cc: Colin Watson , Eli Zaretskii ,
> linux-...@vger.kernel.org, help-texinfo@gnu.org,
> nabijaczlew...@nabijaczleweli.xyz, g.branden.robin...@gmail.com,
> gr...@gnu.org
> Date: Sat, 08 Apr 2023 21:48:13 +0200
>
> $ find /usr
> Date: Sat, 8 Apr 2023 15:02:59 +0200
> Cc: d...@gouders.net, linux-...@vger.kernel.org, help-texinfo@gnu.org,
> nabijaczlew...@nabijaczleweli.xyz, g.branden.robin...@gmail.com,
> gr...@gnu.org
> From: Alejandro Colomar
>
> If you want how symlinks are dereferenced by find(1):
>
> $ man find
> Date: Sat, 8 Apr 2023 00:01:08 +0200
> Cc: d...@gouders.net, linux-...@vger.kernel.org, help-texinfo@gnu.org,
> наб ,
> "G. Branden Robinson" , groff ,
> Colin Watson
> From: Alejandro Colomar
>
> > How do you find the description of, say, "dereference symbolic link"
> > (to take just a ran
> Date: Fri, 7 Apr 2023 09:43:19 -0500
> From: "G. Branden Robinson"
> Cc: alx.manpa...@gmail.com, d...@gouders.net, cjwat...@debian.org,
> linux-...@vger.kernel.org, help-texinfo@gnu.org, gr...@gnu.org
>
> ...which brings me to the other factor, of which I'm more confident: man
> page rend
> Date: Thu, 6 Apr 2023 21:18:22 -0500
> From: "G. Branden Robinson"
> Cc: Eli Zaretskii , d...@gouders.net,
> linux-...@vger.kernel.org, help-texinfo@gnu.org
>
> > Hmm, now that I think, it's probably an issue of coordinating man(1)
> > and less(
> From: Arsen Arsenović
> Cc: Dirk Gouders , alx.manpa...@gmail.com,
> linux-...@vger.kernel.org, help-texinfo@gnu.org
> Date: Wed, 05 Apr 2023 22:38:12 +0200
>
> I've been casually wondering if creating a new format that can host more
> formatting options and uses more precise syntax than 'plai
> Date: Thu, 6 Apr 2023 03:10:59 +0200
> Cc: d...@gouders.net, linux-...@vger.kernel.org, help-texinfo@gnu.org
> From: Alejandro Colomar
>
> > This last sentence is a misunderstanding. The goal of Texinfo is not
> > to improve the man pages. Texinfo is a completely different approach
> > to sof
> Date: Thu, 6 Apr 2023 08:44:17 +0200
> From: to...@tuxteam.de
>
> There will be differences in the renderers. Neither info nor man
> can do pics, HTML and PDF can.
The Emacs Info reader does display the pictures when they are
available (and assuming Emacs was built with support for the
correspo
> From: Dirk Gouders
> Cc: Alejandro Colomar , linux-...@vger.kernel.org,
> help-texinfo@gnu.org
> Date: Wed, 05 Apr 2023 20:01:56 +0200
>
> Arsen Arsenović writes:
>
> • In windowing environments lsp does complete resizes when
> windows
> get resized. This
> Date: Wed, 5 Apr 2023 11:21:12 +0200
> From: to...@tuxteam.de
> Cc: help-texinfo@gnu.org
>
> > The future is already here: just use Texinfo manuals for everything.
>
> Not the one I dreamt of. No TLDP man pages. No kernel.org docs.
That's not true, since the Info reader will display man pages
> Date: Wed, 5 Apr 2023 11:03:36 +0200
> From: to...@tuxteam.de
> Cc: help-texinfo@gnu.org
>
> I was dreaming of a world where both doc systems converge
> in a way their respective users don't notice, and we end
> up with a Grand Unified Documentation (GUD) for all things
> free.
The future is al
> Date: Wed, 5 Apr 2023 10:04:02 +0200
> From:
>
> On Wed, Apr 05, 2023 at 08:35:13AM +0300, Eli Zaretskii wrote:
>
> [...]
>
> > Man pages have no means of specifying structure and hyper-links except
> > by loosely-coupling pages via "SEE ALSO" cros
> Date: Wed, 5 Apr 2023 01:45:46 +0200
> Cc: help-texinfo@gnu.org
> From: Alejandro Colomar
>
> With the benefit that you don't need to implement such a system from scratch,
> but just reusing the existing tools (apropos, man, whatis, ...). It seems
> something like what I would have written if
> From: Arsen Arsenović
> Cc: Dave Kemper , alx.manpa...@gmail.com,
> g.branden.robin...@gmail.com, help-texinfo@gnu.org
> Date: Tue, 10 Jan 2023 14:28:16 +0100
>
> Also, I didn't realize this before it was mentioned here, but yes,
> ``(info)Help'' indeed comes with EMACS. Perhaps we should inc
> From: Dave Kemper
> Date: Mon, 9 Jan 2023 15:36:44 -0600
> Cc: ar...@aarsen.me, alx.manpa...@gmail.com, g.branden.robin...@gmail.com,
> help-texinfo@gnu.org
>
> On 1/9/23, Eli Zaretskii wrote:
> > It is not a coincidence that the GNU project deprecated man pa
> From: Dave Kemper
> Date: Mon, 9 Jan 2023 00:01:33 -0600
> Cc: Alejandro Colomar ,
> "G. Branden Robinson" , help-texinfo@gnu.org
>
> On 1/7/23, Arsen Arsenović wrote:
> > Alejandro Colomar writes:
> >> How about adding the following:
> >>
> >>For readers more familiar with manual pages
> From: Jean-Christophe Helary
> Date: Sun, 4 Dec 2022 23:26:37 +0900
>
> I'm looking at the GNU texinfo page and I can't find a summary of the changes
> made in 7.0.
>
> Is it available somewhere else ?
In NEWS.
> From: Arsen Arsenović
> Cc: Patrice Dumas , Eli Zaretskii ,
> help-texinfo@gnu.org
> Date: Sat, 26 Nov 2022 21:40:53 +0100
>
> I was still interested in indexing @itemx', so I tried:
>
> @table @code
> @vindex ABC
> @item ABC
> @vindex DEF
>
> From: Gavin Smith
> Date: Fri, 25 Nov 2022 22:12:21 +
>
> I'm starting to think that it should be index entries *before* the @item that
> are associated with the @item, not after it. I feel this may be easier to
> implement. This would leave the Info output unaltered.
This is how things
> From: Gavin Smith
> Date: Mon, 21 Nov 2022 18:43:18 +
> Cc: Arsen Arsenović ,
> help-texinfo@gnu.org
>
> On Mon, Nov 21, 2022 at 03:23:58PM +0200, Eli Zaretskii wrote:
> > The index entries should precede the first @item, not be after it. Maybe
> > doin
> From: Arsen Arsenović
> Cc: help-texinfo@gnu.org
> Date: Mon, 21 Nov 2022 14:29:32 +0100
>
> > The index entries should precede the first @item, not be after it. Maybe
> > doing so doesn't work in this case, but you should move the index entries
> > before the @item/@itemx lines regardless, si
> From: Arsen Arsenović
> Date: Sun, 20 Nov 2022 19:44:30 +0100
>
> In the GCC documentation, a construct that often appears is
>
> @table @gcctabopt
> @item -Wpedantic
> @itemx -pedantic
> @opindex pedantic
> @opindex Wpedantic
> @opindex Wno-pedantic
>
> The problem with this, tho
> Date: Sat, 09 Oct 2021 21:50:08 -0500
> From: Jacob Bachmeyer
> CC: Alan Mackenzie , help-texinfo@gnu.org
>
> From my viewpoint, it seems that Alan wants some kind of equivalence
> table, such that ASCII backtick and single quote will match the Unicode
> curly quotes when typed into an I-sea
quotes, which don't exist on my keyboard. Thus I cannot
> search for `foo' in any reasonable way in Emacs.
>
> Also, the display of these Unicode punctuation characters is awkward and
> ugly on my Linux console.
>
> The Emacs maintainer, Eli Zaretskii, has expressed his
> Date: Sun, 12 Sep 2021 11:03:54 +0200
> From: Patrice Dumas
>
> It is already the case, in the sense that @menu are not needed anymore.
> In Info output, menus are automatically generated if they do not exist.
> In HTML the new default does not require menus. In addition, there is a
> "tree tr
> Date: Sun, 12 Sep 2021 03:38:24 -0400
> From: Mike Frysinger
> Cc: help-texinfo@gnu.org
>
> > Not the answer you expected, but Emacs has a command that creates the
> > menus for you.
>
> i saw mention of that shortcut in the manual, but as you can imagine, that's
> not terribly interesting to
> Date: Sat, 11 Sep 2021 23:20:00 -0400
> From: Mike Frysinger
>
> i couldn't easily find an answer in the archives or manual, so feel free to
> point me to docs or discussions that i missed. surely this can't be a new
> idea that i managed to come up with myself. or there's a good reason that
> From: Gavin Smith
> Date: Fri, 13 Aug 2021 16:54:55 +0100
> Cc: "help-texinfo@gnu.org"
>
> > In the example below, should I place a0 or a1 to get a reference to item
> > ``First one''.
> >
> > @itemize
> > @anchor{a0}
> > @item
> > @anchor{a1}
> > First one
> > @end itmize
> >
> > PS : Pleas
> From: lisa-as...@perso.be
> Date: Tue, 13 Jul 2021 05:22:38 +0200 (CEST)
>
> Is it correct to say that when using `@ref ` there are only two possibilities.
>
> (1) reference to a node
> (2) reference to an anchor.
Yes. It's true for all types of cross-reference directives, not just
for @ref
> Date: Sun, 11 Jul 2021 22:20:07 +0200 (CEST)
> From: excala...@tutanota.com
> Cc: Help Texinfo
>
> 1. Run emacs -q
> 2. Drag sample.info into the Emacs frame
> 3. M-x Info-mode
> 4. M-x rev-b, y
> 5. Select 'Index'
> 6. Select 'the spot'
>
> It takes me to Top.
That's a strange method of acce
> Date: Sun, 11 Jul 2021 18:38:18 +0200 (CEST)
> From: excalamus--- via Users list for the Texinfo documentation system
>
>
> I'm trying to create an @xref to an @anchor. When clicking the reference,
> Emacs says,
>
> "No such node or anchor: x-spot"
>
> I have taken the sample file from (te
> From: Christopher Dimech
> Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org
> Date: Thu, 24 Jun 2021 21:42:10 +0200
>
> It would be a great improvement to have a standard on how we can test
> newer versions of texinfo without affecting the stable version we normally
> use. It makes it very d
> From: Christopher Dimech
> Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org
> Date: Thu, 24 Jun 2021 19:00:29 +0200
>
> I used
>
> cd /home/hagbard/Admir/build/texinfo
> ../../source/texinfo/configure --prefix=/home/hagbard/Admir/bin/texinfo
> make
> sudo make install
The --prefix sets seve
> From: Christopher Dimech
> Date: Thu, 24 Jun 2021 17:53:02 +0200
> Sensitivity: Normal
> Cc: help-texinfo@gnu.org
>
> Ok, I added the texinfo development directory to PATH.
>
> Now getting again to the old problem of texinfo.tex
Why did you need to add some directory to PATH? Did you instal
> From: Christopher Dimech
> Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org
> Date: Wed, 23 Jun 2021 21:40:05 +0200
>
> Does Gnu have a latex construct program to produce documents?
You mean, as opposed to LaTeX that is part of the TeX installation?
Not that I know of, no.
> From: Christopher Dimech
> Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org
> Date: Wed, 23 Jun 2021 20:52:44 +0200
>
> > That would clobber existing installations it TeX Live etc., so it's
> > not a good idea to do that by default, without the user's say-so.
> >
> > > I disagree on the addit
> From: Christopher Dimech
> Date: Wed, 23 Jun 2021 20:20:49 +0200
> Cc: help-texinfo gnu
>
> Of course, but I also give you a point of thought from user perspective.
>
> That way, the texinfo installation could also handle the additional
>
> make TEXMF=/your/texmf install-tex
> texinfo.tex is
> From: Christopher Dimech
> Cc: pertu...@free.fr, help-texinfo@gnu.org
> Date: Tue, 22 Jun 2021 20:41:16 +0200
>
> That would make the use of macros very limited.
Macros in Texinfo have many problems.
> From: Christopher Dimech
> Date: Tue, 22 Jun 2021 19:52:52 +0200
> Cc: help-texinfo gnu
>
> @macro usubsec {label, titl}
>
> @set lb \label\
> @set tl \titl\
> @ifclear usubsec-no-label
>@unnumberedsubsec @value{lb} @ @value{tl}
> @end ifclear
>
> @ifset usubsec-no-label
> @unnumbereds
> From: Benjamin Fang
> Date: Fri, 11 Jun 2021 17:18:15 +0800
>
> when I compile the code, I get the following error:
>
> -
>
> parsetexi/api.c: In function ‘find_locales_dir’:
> parsetexi/api.c:69:23: error: ‘PACKAGE’ undeclared (first use in this
>
> From: Christopher Dimech
> Cc: help-texinfo@gnu.org
> Date: Fri, 30 Oct 2020 21:45:58 +0100
> Sensitivity: Normal
>
> I am getting the following complaining of makeinfo.
Install some official release of Texinfo, and then try again.
> From: Christopher Dimech
> Date: Fri, 30 Oct 2020 21:02:40 +0100
> Sensitivity: Normal
>
> I am trying to install texinfo using the development source tree.
>
> git clone https://git.savannah.gnu.org/git/texinfo.git
>
> I am having problem with the configure part. There is no configure and a
> From: Christopher Dimech
> Date: Fri, 23 Oct 2020 23:00:40 +0200
> Cc: help-texinfo gnu
>
> Pdf are very important in business settings, and because Texinfo allows
> inclusion of mathematical expression (through @math, @tex), the pdf output
> is very useful.
Texinfo doesn't have a separate PD
> From: Jean-Christophe Helary
> Date: Sat, 25 Jan 2020 18:19:48 +0900
>
> >> But then, what's the point having a @lisp block ?
> >
> > See the explanation of this in the Texinfo manual, in the "@lisp"
> > node.
>
> I see. I did not understand that part when I first read it. So it is like a
>
> From: Jean-Christophe Helary
> Date: Sat, 25 Jan 2020 11:06:01 +0900
>
> And since that was not the case, what I did was generate the indentation in a
> lisp buffer and paste the result within the @lisp block. Since the texinfo
> processor does not seem to change the indentation that was all
> From: Jean-Christophe Helary
> Date: Sat, 25 Jan 2020 10:51:52 +0900
>
> > Sorry, I don't know what you mean. This sounds like an Emacs question
> > (if you are using Emacs).
>
> Yes, but.
>
> @lisp
>
> (lispy stuff)
>
> @end lisp
>
> The *output* is not indented at all. I'd have expecte
> From: Aleksey Midenkov
> Date: Tue, 30 Jul 2019 22:31:27 +0300
> Cc: Eli Zaretskii , help-texinfo@gnu.org
>
> I don't know what Hamm is, but that would help.
>
> https://www.electrictoolbox.com/debian-release-names/
>
> Of course you both don't know a
> From: Gavin Smith
> Date: Tue, 30 Jul 2019 12:02:56 +0100
> Cc: Eli Zaretskii , help-texinfo@gnu.org
>
> On 7/30/19, Aleksey Midenkov wrote:
> > No, I don't see them in menu items like on screenshot above. They were in
> > places of asterisks. So how to make
> From: Aleksey Midenkov
> Date: Tue, 30 Jul 2019 00:09:54 +0300
> Cc: help-texinfo@gnu.org
>
> What do you mean by "numbers"? I don't think the stand-alone Info
> reader was ever numbering menu items, if that's what you mean.
>
> Yes, it has numbers. Like I said it was in Hamm for sure (1998
> From: Aleksey Midenkov
> Date: Mon, 29 Jul 2019 12:41:10 +0300
>
> I still wonder why links became underlined and lost their numbers. It was
> very easy to just type 1-9 from
> keyboard and get into what you want. I don't remember when it was changed,
> but it better variant was in Hamm
> (so
> From: "Christopher Dimech"
> Cc: "Patrice Dumas" , help-texinfo@gnu.org
> Date: Mon, 22 Jul 2019 19:30:55 +0200
>
> In what context do you use the second argument and what does it do
> exactly? As Patrice said it does nothing for pdf. My understanding
> is that one uses it for display purposes
> Date: Mon, 22 Jul 2019 16:49:50 +0200
> From: Patrice Dumas
> Cc: help-texinfo gnu
>
> in general I would suggest not using an @*ref command with a non
> empty second argument.
I don't understand why. FWIW, I use it quite a lot, and find it very
useful.
> From: Jean-Christophe Helary
> Date: Wed, 29 May 2019 14:05:48 +0900
>
> Don't bother. I found where to put it: inside the folder where I had the texi
> files.
>
> And it works perfectly well.
>
> Is there a reason why the texinfo.tex file that's distributed with the emacs
> code has an iss
> Date: Wed, 6 Mar 2019 18:52:16 +
> From: Alan Mackenzie
>
> @itemize @w{}
> @item
> @table @asis
> @item Style
> @itemx File Style@footnote{In earlier versions of @ccmode{}, a File
> Style setting took precedence over any other setting apart from a File
> Local Variable setting.}
> @itemx T
> From: Gavin Smith
> Date: Sat, 2 Mar 2019 20:56:07 +
> Cc: help-texinfo@gnu.org
>
> On Thu, Feb 28, 2019 at 11:40:26AM +0900, Jean-Christophe Helary wrote:
> > I'm using the same parameters for the intro, the emacs manual and the lisp
> > reference:
> >
> > HTML_OPTS = --html --css-ref="
> From: David Malcolm
> Cc: help-texinfo@gnu.org
> Date: Fri, 15 Feb 2019 14:03:26 -0500
>
> > Why not use @anchor and @xref? Those should produce visible links.
>
> I'm hoping for some kind of way to get the toolchain to automatically
> generate the HTML I want without having to touch all of t
> From: David Malcolm
> Date: Thu, 14 Feb 2019 17:26:59 -0500
>
> I'm a GCC developer; we use texinfo for our documentation.
>
> GCC has a lot of options, so it's very useful to be able to provide
> users with URLs to *specific* options in our documentation.
>
> For a long time I didn't think t
> Date: Wed, 20 Jun 2018 19:27:58 +0200
> From: Andreas Falkenhahn
> CC: help-texinfo@gnu.org
>
> > There are 2 commands in Texinfo that help TeX hyphenate where its
> > built-in wisdom fails. Read all about them in the node "@-
> > @hyphenation" of the Texinfo manual.
>
> Thanks, but those don
1 - 100 of 229 matches
Mail list logo
