From: Eli Zaretskii <eliz@gnu.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: 2975@debbugs.gnu.org, winkler@gnu.org, Karl Berry <karl@freefriends.org>
Subject: bug#2975: texinfo-master-menu and emacs.texi
Date: Thu, 08 Dec 2011 07:20:39 -0500 [thread overview]
Message-ID: <E1RYcxr-0002GW-6k@fencepost.gnu.org> (raw)
In-Reply-To: <877h27gxh2.fsf@gmail.com> (message from Štěpán Němec on Thu, 08 Dec 2011 11:38:01 +0100)
> From: Štěpán Němec <stepnem@gmail.com>
> Cc: "Roland Winkler" <winkler@gnu.org>, 2975@debbugs.gnu.org
> Date: Thu, 08 Dec 2011 11:38:01 +0100
>
> On Thu, 08 Dec 2011 07:17:40 +0100
> Eli Zaretskii wrote:
>
> >> > Maybe the better course here is to deprecate it, seeing how noone seems
> >> > interested in fixing it (if it can be fixed).
> >
> > Define "fixed". Which of the current misfeatures are urgent to fix?
>
> I'd say the fact that OT1H `texinfo-master-menu' is recommended as "the
> primary command" in the Texinfo manual (info "(texinfo)Updating Commands"),
> and OTOH it (sometimes?) breaks things, is a rather urgent-to-be-fixed
> misfeature.
The simplest fix would be to remove the updating of the @node lines.
Would anyone object? Karl?
> I think it's very important that there is a clear recipe for maintaining
> Texinfo documentation which people not interested in the details or
> implementation of Texinfo (== the vast majority of Texinfo writers) can
> easily find and go by.
That is a separate and non-trivial project. Texinfo Mode has a lot of
commands, some of which cater to specific workflows and organizations
of manuals. Making a coherent set of instructions for people who are
"not interested in the details" is not an easy task. It certainly
doesn't affect only Emacs.
However, since this discussion _is_ in the context of Emacs, let me
say this: FWIW, most changes I do in the Emacs docs do not justify
using any of the commands discussed in this bug report and in the
parallel thread on emacs-devel. I just make the changes by hand. I
believe others do that as well. There are rare situations when I use
the commands discussed here, typically close to a release when there's
a need to make sure every menu is up to date. E.g., I didn't even
remember the existence of texinfo-multiple-files-update until I bumped
into a comment in emacs.texi, although I myself added that comment
several years ago.
I guess I'm saying that the importance of these commands in the
context of maintaining Emacs documentation is somewhat exaggerated in
this thread, to say the least ;-)
next prev parent reply other threads:[~2011-12-08 12:20 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 [this message]
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
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=E1RYcxr-0002GW-6k@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=2975@debbugs.gnu.org \
--cc=karl@freefriends.org \
--cc=stepnem@gmail.com \
--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).