unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 2975@debbugs.gnu.org
Subject: bug#2975: texinfo-master-menu and emacs.texi
Date: Wed, 07 Dec 2011 15:43:50 -0500	[thread overview]
Message-ID: <jwvobvk9kz1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20191.48632.665251.448872@gargle.gargle.HOWL> (Roland Winkler's message of "Wed, 7 Dec 2011 13:26:48 -0600")

> Thanks...Now I am yet more confused. I thought I look into
> emacs.texi because I assumed that this info manual has been updated
> continuously in recent years and this updating has been done with
> the editor of my choice which is emacs. So what have people done who
> contributed to the emacs info manual to work around these
> difficulties? Which parts of emacs' texinfo support do what they are
> supposed to do and which parts seem to be malfunctioning?

I'm pretty sure texinfo-master-menu is not used for that, indeed.
I think "update all menus" is the more common helper command.

IIRC it also suffered from problems where it adds data to "Node"s which
should better not be added at all, so makeinfo can auto-fill it for you
(and makeinfo actually complains about what texinfo-master-menu puts
there).

Maybe the better course here is to deprecate it, seeing how noone seems
interested in fixing it (if it can be fixed).


        Stefan





       reply	other threads:[~2011-12-07 20:43 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       ` Stefan Monnier [this message]
2011-12-07 21:19         ` bug#2975: texinfo-master-menu and emacs.texi 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
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=jwvobvk9kz1.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=2975@debbugs.gnu.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).