On Sun, Oct 06, 2024 at 08:30:45PM +0100, Gavin Smith wrote:
> Disabling it, the sidebar is updated correctly. Here's the full change,
> including your change, that appears to produce the correct behaviour:
...
> I'll probably commit this in a day or two to giv
On Sun, Sep 22, 2024 at 11:05:04AM -0400, Benjamin Kalish wrote:
> And now I can't reproduce the problem with the sidebar even when I try!
>
> To get the expected behavior with the index the following seems to be
> working for me. In the function cache_index_links (info.js line 147)
> replace:
>
On Fri, Sep 06, 2024 at 10:07:15AM +0200, Patrice Dumas wrote:
> > P.S. The `INSTALL.generic' file opens with
> >
> > Basic Installation
> > ==
> >
> > The following shell commands:
> >
> >test -f configure || ./bootstrap
> >./configure
> >mak
On Fri, Sep 27, 2024 at 11:15:48AM +0800, sheng ling wrote:
> Hello,
>
> I noticed that --show-options was removed in info 7.0.3 help output, but I
> still can use the it now. Will it be totally removed in the future?
No, it will not be removed in the future.
I removed it from the help output be
On Thu, Sep 19, 2024 at 03:38:12PM -0400, Benjamin Kalish wrote:
> Two related but distinct questions:
>
> 1. How can I change the index output to contain only the first column
> (index entry names linking to to the points on the page where the index
> entries occurs) and excluding the second colu
On Wed, Sep 18, 2024 at 10:24:42AM -0400, Benjamin Kalish wrote:
> I'm wondering if there is a way to add a level to Texinfo's hierarchy, so
> that there is a level below subsubsection. I'm including files
> using @include, @lowersections and @raisesections, and occasionally I
> "bottom out" and en
On Tue, Sep 10, 2024 at 08:51:57PM +0200, Patrice Dumas wrote:
> On Tue, Sep 10, 2024 at 06:50:35PM +0300, Eli Zaretskii wrote:
> > > Yes, this code appears never actually to have been tested on the platform
> > > this code was for.
> >
> > That's not true. My MinGW port of Texinfo includes a ful
On Tue, Sep 10, 2024 at 10:20:07AM -0400, Benjamin Kalish wrote:
> 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 install
>
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 'pc_initialize_terminal':
> pcterm.c:1297:37: error: assignment to 'int (*)(void)' from
> incompatib
On Tue, Sep 03, 2024 at 10:55:33AM +0200, Patrice Dumas wrote:
> On Tue, Sep 03, 2024 at 07:28:17AM +0100, Gavin Smith wrote:
> >
> > You've convinced me. I think we should change it for @displaymath but
> > not for inline @math as the line breaks there are not meanin
On Tue, Sep 03, 2024 at 01:52:40AM +0200, Rudolf Adamkovič wrote:
> Yes, `lynx' is breaking it as "words in prose", which is what you see.
> That does not work for more complex LaTeX, such as longer derivations,
> more complex systems of equations, and so on.
>
> Consider the following proof, rend
On Fri, Aug 30, 2024 at 10:32:26AM +0200, Rudolf Adamkovič wrote:
> Another point of friction was MathJax, namely its *hard-coded*
> configuration. I ended up pointing `MATHJAX_SCRIPT' to a dummy file,
> and then configuring and loading MathJax myself in `EXTRA_HEAD'.
I don't know what your probl
On Wed, Jul 31, 2024 at 03:41:02PM +0200, Rahguzar wrote:
> While this is true, I thought this might be the easier change. We just
> need some markers. Even if I not handled, these markers wouldn't make
> the presentation worse to a noticeable extent and Emacs being Emacs the
> required changes can
On Wed, Jul 31, 2024 at 11:31:15AM +0200, Rahguzar wrote:
> Hi,
>
> I am trying to build an info manual for the SageMath project. The manual
> functions very well except those parts which include a lot of
> mathematical notation. I want to ask if there are ways to improve the
> presentation of the
On Sun, Jun 02, 2024 at 10:55:26AM +0200, Patrice Dumas wrote:
> On Sun, Jun 02, 2024 at 07:09:50AM +, Jean-Christophe Helary wrote:
> > Ok. I'm using Texinfo 7.1 from brew (macOS) and with the same file and
> > same command I get "Previous", "Up", "Top" and "Footnotes".
> >
> > I guess there
On Sun, Mar 17, 2024 at 02:27:11PM +0100, pertu...@free.fr wrote:
> > The code that appears to strip the comment out is very short and probably
> > not the main source of complexity in the Emacs Lisp program:
> I am not sure that it is that code, as texi5 is defined by, I believe
>
> let ((texi
On Sat, Mar 16, 2024 at 05:48:39PM +0200, Eli Zaretskii wrote:
> > 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 int
On Sun, Mar 17, 2024 at 12:29:01PM +0100, pertu...@free.fr wrote:
> 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
> > suggest how to achieve the same with texi2any customizations, I can
> > assure you that we in
On Sat, Mar 16, 2024 at 03:13:04PM +0100, pertu...@free.fr wrote:
> My last important interrogation is about CSS. The whole CSS added by
> texi2any is removed, instead of using the possibility offered by the
> command-line. My feeling is that what is done right now would be better
> achieved eit
On Fri, Mar 15, 2024 at 09:42:28AM +0200, Eli Zaretskii wrote:
> > What we envisionned, instead, was to provide with the HTML customization
> > API to do the kind of modifications you want to do. I can imagine a
> > number of reasons why this solution is not that attractive for your use
> > case,
On Wed, Mar 13, 2024 at 09:25:44PM +0200, Eli Zaretskii wrote:
> > Nobody complained about this breaking any stability.
>
> Ha! the amount of grief those changes caused the Emacs maintainers is
> beyond complaining. We have a script that massages the produced HTML
> manuals for the Web site, and
On Tue, Mar 12, 2024 at 10:04:11PM +0100, Arsen Arsenović wrote:
> Hi Eli,
>
> [my apologies - I did not use a wide reply, so I am reposting this.
> sorry for the inconvenience]
>
> Eli Zaretskii writes:
>
> > Before making this change, please look at the manuals posted on the
> > GNU Software
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, emitting the title name
> is redundant, and should likely be replaced with simply the manual name
> (sin
On Mon, Feb 12, 2024 at 07:17:37PM +0200, Eli Zaretskii wrote:
> > 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.
> >
On Mon, Feb 12, 2024 at 05:40:24PM +0800, Ralph Lin wrote:
This is a follow-up for my last email.
>
> I didn't get your method working with the tex file short-sample-
> zh.texi.
>
> The working method is by installing auctex(a emacs package) and
> use Texing options - Xetex engine, then use C-c
On Tue, Feb 06, 2024 at 07:49:57PM +, Gavin Smith wrote:
> On Tue, Feb 06, 2024 at 03:22:59PM +0800, Ralph Lin wrote:
> > As you just said, I checked the texinfo source code, and the "txi-
> > zh" and "texinfo-zh" do exist, but not for the texinfo v6.8 that
On Tue, Feb 06, 2024 at 03:22:59PM +0800, Ralph Lin wrote:
> As you just said, I checked the texinfo source code, and the "txi-
> zh" and "texinfo-zh" do exist, but not for the texinfo v6.8 that
> I'm currently using.
>
> I added those files into the documentation source;
>
> and I run the texi2a
On Mon, Feb 05, 2024 at 02:48:15PM +, ralphli...@hotmail.com wrote:
> To whom it might concern:
>
> I have some problems on translating the Emacs manual, a texinfo document,
> to Chinese.
>
> Specifically, when I use the following command:
>
> texi2pdf emacs.texi -o emacs.pdf
>
On Mon, Jan 29, 2024 at 11:34:32PM +, Mekeor Melire wrote:
> Hello,
>
> Emacs Org-Mode's manual "org" has a chapter called
>
> 15.3.1 Bibliography options in the “biblatex” and “csl” export
> processors
>
> You can find it online here:
>
>
> https://orgmode.org/manual/Bib
On Thu, Jan 11, 2024 at 10:03:29PM +0200, Eli Zaretskii wrote:
> > 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.o
On Thu, Jan 11, 2024 at 09:26:51PM +0200, Eli Zaretskii wrote:
> > The Info output, I believe. Suppose there is a cross-reference to a node
> > in the Emacs manual, "Select Buffer". This would appear in Info output
> > as "*note (emacs)Select Buffer::." The English words "Select Buffer"
> > woul
On Thu, Jan 11, 2024 at 02:49:12PM +0100, Patrice Dumas wrote:
> Having nodes linking to non installed manuals is, in general, an issue.
> But I do not think that defaulting to the english manual for non english
> manuals is a good thing to do. Instead, it could be confusing,
> especially if the m
On Thu, Jan 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 node names even if
> > they
On Sat, Jan 06, 2024 at 10:41:11PM +0200, Eli Zaretskii wrote:
> > There's a limit to how many languages one person can read, so they won't
> > need dozens of such directories.
>
> I was thinking about automatic computation of Info-directory-list, the
> way we have in Emacs now. That might need t
On Sat, Jan 06, 2024 at 10:26:29PM +0200, Eli Zaretskii wrote:
> > 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
&g
On Sat, Jan 06, 2024 at 09:24:14PM +0200, Eli Zaretskii wrote:
> > It's up to people writing the Texinfo manuals what they put for
> > @dircategory. In practice it seems that there aren't any well-followed
> > conventions for this so top-level dir files end up quite disorganised.
> >
> > There ar
On Sat, Jan 06, 2024 at 03:57:24AM -0800, Stefan Kangas wrote:
> Eli Zaretskii writes:
>
> >> If that’s the case, what about using “Translated manuals” for now,
> >> since the number of translated manuals is very low?
> >
> > I'd say the other way around: as long as we have very few
> > translati
On Sat, Jan 06, 2024 at 01:49:53PM +, Jean-Christophe Helary wrote:
> Thinking out loud here, but @node currently requires the node-name
> argument and has next/preious/up optional argument. It seems to me that
> most of the issues would be fixed by adding a fifth argument that acts
> like t
On Sat, Jan 06, 2024 at 12:25:55PM +, Jean-Christophe Helary wrote:
> I forgot. If I understand texinfo properly, if the manual name is
> translated (and if the manual is translated) it is enough that the node
> name is the same as in the target manual, so either both untranslated,
> or both
On Sat, Jan 06, 2024 at 09:37:03AM +, Jean-Christophe Helary wrote:
> >> Also, we will have to translate @node, because they appear in the
> >> Section index. I see that they were kept in English in the SES manual.
> >
> > If we translate @node names, links from the doc strings and
> > cross-m
On Sat, Jan 06, 2024 at 10:36:28AM +0200, Eli Zaretskii wrote:
> > Would @author be also used for the translator?
>
> @author is a TeX command and goes into the printed version. For
> translation, we'd need a separate directive, I think, since a
> translator is not the author. Again, this is som
On Sat, Jan 06, 2024 at 04:40:41AM +, Jean-Christophe Helary wrote:
> > I wasn't talking about the manuals. But even for the manuals there
> > are some issues that need to be considered. For example: what do we
> > do with the info/dir file for these translated manuals? what should be
> > @di
On Sun, Dec 31, 2023 at 03:08:22PM +0200, Eli Zaretskii wrote:
> We have current-iso639-language, but its value is a 2-letter string,
> the first 2 characters of the locale's name. So I think this should
> be a new variable, and Info-documentlanguage sounds like a good
> candidate.
Done in commit
On Sun, Dec 31, 2023 at 08:52:20AM +0200, Eli Zaretskii wrote:
> Btw, what exactly does makeinfo produce for cross-references when
> @documentlanguage is not en_US? Is the "*note" thing still produced,
> or is it replaced by something else? I'm guessing that "*note" is
> still produced, since the
On Sat, Dec 30, 2023 at 06:38:07PM +0100, Patrice Dumas wrote:
> The level could depend on the split option, the document seems to be
> split at sections.
Yes, it appears that the section toc is needed if the nodes are in a
different HTML file, but not needed/wanted if they are in the same file.
On Sat, Dec 30, 2023 at 07:04:52PM +0100, Patrice Dumas wrote:
> On Sat, Dec 30, 2023 at 02:48:17PM +, Daniel Cerqueira wrote:
> > Hi!
> >
> > I am writing a info book in Portuguese (@documentlanguage pt). The book
> > is totally in Portuguese, except that when I do a cross-reference with
> >
On Sun, Nov 12, 2023 at 07:23:41PM +, Gavin Smith wrote:
> There is actually a problem with @ftable and @vtable. If you put an
> @anchor on an @item line there, then it is the text of an index entry,
> which is a real problem.
Further to this, if @anchor should be allowed inside
On Tue, Nov 07, 2023 at 11:29:24AM +0100, Patrice Dumas wrote:
> On Mon, Nov 06, 2023 at 07:29:50PM +0000, Gavin Smith wrote:
> > On Sun, Nov 05, 2023 at 11:30:42AM +, Ihor Radchenko wrote:
> > > May someone please explain the correct usage of @anchor in the above
> &g
On Sun, Nov 05, 2023 at 11:30:42AM +, Ihor Radchenko wrote:
> However, there is a warning being produced when @anchor is found on the
> same line with an item:
>
> org.texi:15975: warning: @anchor should not appear on @item line
>
> The problematic .texi source is
>
> @table @asis
>
On Wed, Nov 01, 2023 at 02:17:35PM +, Oleander wrote:
> Hello everyone,
>
> which command do you use to represent input which is based on text
> presented by the system, such as the names of menus and menu items?
>
> I write documentation for my team at work. When I want to point out that
> a
On Tue, Aug 29, 2023 at 08:22:19PM +, Oleander wrote:
> Hello everyone!
>
> Does texinfo suit other works that are not software-related like sys
> admin documentation, lectures, long essays, fictional/non fictional
> books? From what I've read in the manual so far, it is possible to
> produce
On Tue, Aug 08, 2023 at 01:17:06PM +, Alan Mackenzie wrote:
> Hello, Gavin.
>
> On Mon, Aug 07, 2023 at 23:25:42 +0100, Gavin Smith wrote:
> > On Mon, Aug 07, 2023 at 09:16:36PM +, Alan Mackenzie wrote:
>
> [ ]
>
> > To get the menus output in HTML
On Mon, Aug 07, 2023 at 09:16:36PM +, Alan Mackenzie wrote:
> Hello, help-texinfo.
>
> In texinfo-7.0.3, my main menu (a long menu starting with @menu and
> ending with @end menu) is not getting output in my HTML output. This is
> failing to happen even with an older version of my .texi file
On Sat, Jan 28, 2023 at 10:00 PM Gavin Smith wrote:
>
> On Thu, Jan 19, 2023 at 09:21:59AM +0100, Vitezslav Crhonek wrote:
> > Hi,
> >
> > Releases of texinfo used in Fedora can be found here (texinfo-4.2
> > included):
> > https://src.fedoraproject.org/look
On Sun, Jul 09, 2023 at 04:20:41PM +0200, Andreas Falkenhahn wrote:
> I don't know if it's related to the new @link command or if it's a general
> new feature but I've observed the following:
>
> When using texi2pdf with my old version of texinfo.tex, only the page number
> of entries in the tab
On Thu, Jun 29, 2023 at 09:17:18PM +0200, Andreas Falkenhahn wrote:
> Hi,
>
> I've found a problem now with the new @link command. It happens when using
> constructions like this:
>
> @example
> @link{One, One}
> Two
> @link{One, Three}
> @end example
>
> When converting such a texi to pdf, the
On Sun, May 21, 2023 at 09:48:13PM +0200, Bruno Haible wrote:
> Hi,
>
> Diffs of .texi files are often hard to review, because the committer has
> reformatted (refilled) the paragraph.
>
> The Linux man-pages project has this guidance to avoid this problem (in
> groff -mandoc source, not in .texi
On Wed, May 03, 2023 at 10:52:58PM +0200, Andreas Falkenhahn wrote:
> On 03.05.2023 at 17:39 Gavin Smith wrote:
>
> > That should be the case already? The green was just from my example
> > code setting \linkcolor, but if you take that out then it should be
> > the defaul
On Tue, May 02, 2023 at 07:55:04PM +0200, Andreas Falkenhahn wrote:
> On 04.04.2023 at 23:12 Gavin Smith wrote:
>
> > I've committed a change to texinfo.tex (2023-04-04.21) to implement
> > a new @link command. Please try it and see if it is what you want. It
> > is
On Fri, Apr 07, 2023 at 09:04:03PM +0200, Alejandro Colomar wrote:
> $ time man -w gcc | xargs zcat | groff -man -Tutf8 2>/dev/null >/dev/null
>
> real 0m0.406s
> user 0m0.534s
> sys 0m0.042s
>
> But as others said, I don't really care about the time it takes to format
> the entire document,
On Fri, Apr 07, 2023 at 09:36:10AM +0300, Eli Zaretskii wrote:
> This should be possible, but it flies in the face of the feature
> whereby formatted man pages are kept for future perusal, which is
> therefore faster: if the formatted pages reflect the particular size
> of the pager's window, it is
On Thu, Apr 06, 2023 at 11:14:01AM +0300, Eli Zaretskii wrote:
> > The alternative is, of course, bringing HTML up to par feature-wise
> > (wrt. indices etc), but that'd be on the other end of the extreme, where
> > instead of being too easy to parse and lacking important information,
> > it'd be o
On Thu, Apr 06, 2023 at 11:11:40AM +0300, Eli Zaretskii wrote:
> How do you find the description of, say, "dereference symbolic link"
> (to take just a random example from the Emacs manual) when the actual
> text of the manual include neither this string nor matches for any
> related regular expres
On Thu, Apr 06, 2023 at 08:29:19AM +0200, to...@tuxteam.de wrote:
> > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Info-Format-Specification.html
>
> As a thought experiment: what would it take for that
> reference above to (also) open a local info viewer?
>
> The technical par
On Wed, Apr 05, 2023 at 12:11:44PM +0300, Eli Zaretskii wrote:
> > 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
(switching from help-texinfo to bug-texinfo)
On Mon, Mar 06, 2023 at 10:45:05PM +0900, Jean-Christophe Helary wrote:
> >> I found the example with a nested @def* block interesting:
> >>
> >
> >> https://luis-felipe.gitlab.io/texinfo-css/Elements.html#Definitions
> >>
> >
> >> It reminded me of
On Sun, Mar 05, 2023 at 03:26:17PM +, Luis Felipe wrote:
> Hi,
>
> Just sharing a link to version 2.0.0 of my style sheet for documentation
> generated with Texinfo 7's makeinfo program.
>
> This new version comes with light and dark color schemes that are activated
> automatically based on
On Tue, Oct 19, 2021 at 05:14:28PM +, Alan Mackenzie wrote:
> Hello, Gavin.
>
> On Mon, Oct 18, 2021 at 20:50:50 +0100, Gavin Smith wrote:
> > I will look at the documentation and other issues you raise.
>
> Thanks! I'll look forward to that.
Hello Alan, I am
On Sat, Feb 11, 2023 at 08:11:22PM +0100, Patrice Dumas wrote:
> On Sat, Feb 11, 2023 at 11:59:07AM +0000, Gavin Smith wrote:
> >
> > I've commited changes to texinfo.tex to introduce @defblock, @deflinex
> > and @deftypelinex. @deflinex is like @deffnx and @deftypelin
On Sat, Feb 11, 2023 at 11:59:08AM +, Gavin Smith wrote:
> I have gone off the idea of using @macro for this. I am thinking a
> more limited command would be better, as mentioned in an earlier message
I've committed a change to texinfo.tex for a new command @newdef. Ex
On Fri, Feb 10, 2023 at 01:35:17PM +, Gavin Smith wrote:
> With the patch below, the following input outputs as you would expect.
>
> \input texinfo
>
> @defblock
> @deflinex Functionoid bar (args)
> @deflinex Monoid bar2 (args, nineyy)
> hello
>
> @end def
On Fri, Feb 10, 2023 at 04:24:00PM +0100, Patrice Dumas wrote:
> I have understood that the use can use any index command, simply by
> adding it before the @deflinex, but I did not understand where the user
> definition comes in?
>
> > \input texinfo
> >
> > @defblock
> > @deflinex Functionoid ba
On Thu, Feb 02, 2023 at 07:14:53PM +, Gavin Smith wrote:
> I imagine that there would be another type of block
> like @defblock ... @end defblock which could contain the @def lines,
> which would allow the same formatting without the use of @macro.
I expect that I'll be able to
On Mon, Nov 21, 2022 at 11:37:10AM -0800, Raymond Toy wrote:
> I'm converting some old documents written with Scribe. The conversion is
> pretty straightforward since the syntax between Scribe and Texinfo are
> really pretty close.
>
> However, I've run into a small issue. The original Scribe di
On Sun, Feb 05, 2023 at 01:44:22PM +0100, Andreas Falkenhahn wrote:
> Hi,
>
> I'm wondering if it's possible to create named links in Texinfo documents. I
> want to define the text and the target node for the link. E.g. I want to
> define a link which appears as "Click here" in the PDF and when
On Thu, Feb 02, 2023 at 07:14:53PM +, Gavin Smith wrote:
> Yes, we couldn't use @deffn. I am thinking perhaps just @def which
> would be like the \defheaderline macro that you've already discovered
> in texinfo.tex.
On second thoughts, @def clashes badly with \def in TeX
On Tue, Jan 31, 2023 at 09:42:20PM +0100, Arsen Arsenović wrote:
> Consider also a language like Poke, which does not have the usual
> type-name-args syntax, instead opting for ``fun name = (args) type:
> {...}'' for functions, and similarly, ``method name = (args) type:
> {...}'' for methods. It
On Thu, Dec 15, 2022 at 09:17:43PM +, Gavin Smith wrote:
> I've commited a change for an experimental feature to allow this. This
> is in texinfo.tex version 2022-12-15.20 (in git).
>
> Example code:
>
> \input texinfo
>
> @defcodeindex xy
>
On Thu, Jan 19, 2023 at 09:21:59AM +0100, Vitezslav Crhonek wrote:
> Hi,
>
> Releases of texinfo used in Fedora can be found here (texinfo-4.2
> included):
> https://src.fedoraproject.org/lookaside/pkgs/texinfo/
>
> Given to Fedora guidelines they all should be unmodified. Later releases
> are st
On Fri, Jan 20, 2023 at 11:01:03PM +0100, Arsen Arsenović wrote:
> >> What's the idiomatic way to make such an alias? Is there any currently?
> >
> > I don't know if this counts as idiomatic or recommended, just that there
> > doesn't seem to be any other better way of doing it.
>
> This seems to
On Fri, Jan 20, 2023 at 09:13:13PM +0100, Arsen Arsenović wrote:
> Hi,
>
> I'm working on the GCC manual again (finally!), and I'm trying to
> harmonize it on using definition commands for built-ins et al. For
> writing convenience, as well as consistency, I'd like to define aliases
> for commonl
On Wed, Jan 18, 2023 at 01:30:01PM -0800, Rob Krum wrote:
> Greetings,
> I've noticed that texinfo release 4.2 is missing from gnu's ftp archives,
> but the manual still exists for it in the old-gnu archive. Texinfo 4.2 I
> believe is the latest release that can be used to make binutils 2.16.1a.
>
On Tue, Jan 10, 2023 at 09:39:28PM +0100, Alejandro Colomar wrote:
> I don't have that documentation available. In which package is it?
$ dpkg -S /usr/share/info/libc.info.gz
glibc-doc-reference: /usr/share/info/libc.info.gz
This is on Linux Mint 20.3.
It's also available on the website:
https
On Tue, Jan 10, 2023 at 09:14:35PM +0100, Alejandro Colomar wrote:
> I'm curious about how away from man(7) pages that hypothetical GNU OS is.
> Would you use info pages for libc functions?
>
> So far, I tried to find printf(3) with info(1), but `info printf` brings me
> to the documentation for p
On Tue, Jan 10, 2023 at 02:28:16PM +0100, Arsen Arsenović wrote:
> Also, I didn't realize this before it was mentioned here, but yes,
> ``(info)Help'' indeed comes with EMACS. Perhaps we should include a
> copy in the Texinfo distribution too, or encourage downstreams to
> extract info.info out of
On Tue, Jan 10, 2023 at 02:46:10PM +0200, Eli Zaretskii wrote:
> > 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 coi
On Mon, Jan 09, 2023 at 03:36:44PM -0600, Dave Kemper wrote:
> All I'm saying is, don't confuse YOUR (collective help-texinfo)
> worldview with THE worldview. The main points are: (a) the info
> program can accommodate both types of users; and (b) two small
> additions to the info man page will le
On Sat, Jan 07, 2023 at 11:40:29PM +, Gavin Smith wrote:
> > This documentation describes the stand-alone Info reader which you can
> > use to read Info documentation.
> >
> >If you are new to the Info reader, then you can get started by typing
> > '
On Mon, Jan 09, 2023 at 06:52:44PM +0200, Eli Zaretskii wrote:
> It's an obscure capability that is useful in marginal situations. A
> large manual piped like this will present a humongously long linear
> text, and I doubt that the result will be a convenient read. It's
> again not an incident th
On Sat, Jan 07, 2023 at 11:45:32PM +0100, Arsen Arsenović wrote:
> >> That said, that could be
> >> done, if others agree, but I believe a better experience can be created
> >> by making the info format viewers themselves more accessible for people
> >> more used to pagers, or otherwise un-adapted
On Sat, Jan 07, 2023 at 11:37:35PM +0100, Alejandro Colomar wrote:
> Hi Arsen,
>
> On 1/7/23 21:33, Arsen Arsenović wrote:
> > Hi Alex,
> >
> > Alejandro Colomar writes:
> >
> > > Hello,
> > >
> > > As someone with zero knowledge of how info(1) works, but considerable
> > > knowledge
> > > of
On Sat, Jan 07, 2023 at 09:33:40PM +0100, Arsen Arsenović wrote:
> Hi Alex,
>
> Alejandro Colomar writes:
>
> > Hello,
> >
> > As someone with zero knowledge of how info(1) works, but considerable
> > knowledge
> > of how to read a manual page (well, there's little to it; less(1) is really
> >
On Wed, Jan 04, 2023 at 05:08:09PM +0700, Nutchanon Wetchasit wrote:
> Hello,
>
> Following is going to be an unusual question,
> concerning a very specific usage scenario and requirement
> that intentionally goes against what's so-called
> "best-practices" set by industries-that-must-not-be-named
On Fri, Dec 30, 2022 at 02:47:49PM -0500, Pierce Burger wrote:
> Hello. I would like to request for gnu info to allow scrolling with the j
> and k keys, similar to how it works in vim. I am used to using those keys
> for scrolling and noticed that they dont have another purpose in info.
>
> Thank
On Fri, Dec 16, 2022 at 03:01:06PM -0800, Raymond Toy wrote:
> > You can do this using @deffn and @deffnx instead, at the expense of also
> > needing to specify "Function" on the first line:
> >
> > @deffn {Function} {check-region-query-size} {region}
> > @deffnx {@sansserif{He
On Fri, Dec 16, 2022 at 08:40:43AM -0800, Raymond Toy wrote:
> I tried this out with my translated Scribe document for one entry. The
> entry looks like
>
> @defun {check-region-query-size} {region}
> @defunx {Hemlock Variable} {Region Query Size} @val{30}@useindex{vr}
> description
> @end defun
On Tue, Nov 22, 2022 at 09:56:42PM +, Gavin Smith wrote:
> Interesting to see the Scribe document - I don't think I've seen one
> before.
>
> I think that @deffn and @defvrx etc. could be mixed, although
> the @def* commands have long been an area where changes c
On Thu, Dec 01, 2022 at 03:29:34PM +0100, Arsen Arsenović wrote:
> Hi,
>
> > It looks like gather_previous_items supports @itemx (at least in the
> > Non-XS parser), so I might be able to figure that out tomorrow, sadly, I
> > am out of time for the day. Hopefully, it wouldn't be too hard to
> >
On Sat, Nov 26, 2022 at 11:11:52PM +0100, Patrice Dumas wrote:
> I spotted two cases for which the index entry could also be with the
> table term (in xtables inter_item_commands_in_table test), with a
> comment between index entry and @item or an empty line between index
> entry and @item:
>
> @t
On Sat, Nov 26, 2022 at 03:59:00PM +, Gavin Smith wrote:
> I still haven't put index entries before the very first
> @item in a @table inside the - I need to do something with the
> 'before_item' element.
It should be done now. I tried never adding a 'before_ite
1 - 100 of 502 matches
Mail list logo
