unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 2975@debbugs.gnu.org, Karl Berry <karl@freefriends.org>
Subject: bug#2975: texinfo-master-menu and emacs.texi
Date: Thu, 08 Dec 2011 20:06:45 +0100	[thread overview]
Message-ID: <8739cuhohm.fsf@gmail.com> (raw)
In-Reply-To: <20193.1889.937384.407090@gargle.gargle.HOWL> (Roland Winkler's message of "Thu, 8 Dec 2011 12:52:17 -0600")

On Thu, 08 Dec 2011 19:52:17 +0100
Roland Winkler wrote:

> On Thu Dec 8 2011 Eli Zaretskii wrote:
>> The simplest fix would be to remove the updating of the @node lines.
>> Would anyone object?  Karl?
>
> A TeXnical question: what about using TeX to generate the output? 
> To the best of my knowledge makinfo doesn't care about @node lines
> being up to date or not, it can fix them itself. Does the same hold
> for TeX?

Unless I'm missing something, you already got an answer to this question
in Eli's first reply in this thread:

---
[Roland]
> Of course, I believe that makeinfo can add the info about the node
> pointers. But what about output formats not supported by makeinfo?
> I believe that something like TeX needs them.

[Eli]
TeX doesn't need them.  These pointers are there to allow traversing
the on-line manual, and are not needed for non on-line versions.
---

(Personally I found Eli's explanation confusing -- what does "on-line"
mean here? If it means HTML, makeinfo does support HTML output -- does
it mean it doesn't cope with missing node pointers in the HTML case? If
it means the standard Info manuals, then that's the principal format
supported, isn't it...)

-- 
Štěpán





  parent reply	other threads:[~2011-12-08 19:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191.12232.556454.551166@gargle.gargle.HOWL>
     [not found] ` <E1RYHPD-0000vm-PC@fencepost.gnu.org>
     [not found]   ` <h87h28tgcg.fsf@fencepost.gnu.org>
     [not found]     ` <20191.48632.665251.448872@gargle.gargle.HOWL>
2011-12-07 20:43       ` bug#2975: texinfo-master-menu and emacs.texi Stefan Monnier
2011-12-07 21:19         ` Roland Winkler
2011-12-08  6:17           ` Eli Zaretskii
2011-12-08 10:38             ` Štěpán Němec
2011-12-08 12:20               ` Eli Zaretskii
2011-12-08 14:46                 ` Stefan Monnier
2011-12-10 11:00                   ` Eli Zaretskii
2011-12-08 18:52                 ` Roland Winkler
2011-12-08 18:55                   ` Roland Winkler
2011-12-08 19:06                   ` Štěpán Němec [this message]
2011-12-08 19:37                     ` Eli Zaretskii
2011-12-08 19:59                       ` Štěpán Němec
2011-12-08 20:54                         ` Roland Winkler
2011-12-09  7:28                           ` Eli Zaretskii
2011-12-09  7:48                             ` Roland Winkler
2011-12-10  0:17                           ` Karl Berry
2011-12-10 10:57                             ` Eli Zaretskii
2011-12-09  7:30                         ` Eli Zaretskii
2011-12-08 19:33                   ` Eli Zaretskii
2009-04-12 21:33 bug#2975: `texinfo-master-menu' doesn't work Alan Mackenzie
2011-12-10 12:40 ` Eli Zaretskii
     [not found] ` <837h24mwfs.fsf@gnu.org>
     [not found]   ` <20111211173859.GA2755@acm.acm>
2011-12-11 18:18     ` Eli Zaretskii
2011-12-12 12:25       ` Alan Mackenzie
2011-12-12 13:02         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8739cuhohm.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=2975@debbugs.gnu.org \
    --cc=karl@freefriends.org \
    --cc=winkler@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).