From: Eli Zaretskii <eliz@gnu.org>
To: karl@freefriends.org (Karl Berry)
Cc: stepnem@gmail.com, winkler@gnu.org, 2975@debbugs.gnu.org
Subject: bug#2975: texinfo-master-menu and emacs.texi
Date: Sat, 10 Dec 2011 12:57:09 +0200 [thread overview]
Message-ID: <83borgn18a.fsf@gnu.org> (raw)
In-Reply-To: <201112100017.pBA0Hf4Y028604@sls-af11p1.sea2.superbservers.com>
> Date: Fri, 9 Dec 2011 16:17:41 -0800
> From: karl@freefriends.org (Karl Berry)
> Cc: stepnem@gmail.com, eliz@gnu.org, 2975@debbugs.gnu.org
>
> > So, given that makeinfo can add the info itself when needed, is there
> > really ever any need for listing the node pointers explicitly at all?
>
> If Karl or whoever could answer this question with a clear "no, these
> node pointers are never needed"
>
> I believe Eli answered this, but to reiterate, it is only (very)
> exceptional manuals which might need node pointers.
>
> So if you're asking if texinfo-mode needs to keep supporting them, I
> would say, definitely not. In fact, I think it would be a good thing if
> it didn't. I have seen many authors have unnecessary problems due to
> texinfo-mode inserting the node pointers.
I updated the commentary and the doc strings of the relevant functions
in texnfo-upd.el to the effect that texinfo-update-node and the
commands that call it should only be used if one knows what they are
doing. I also made texinfo-master-menu call texinfo-update-node only
if the prefix arg is numeric, because invoking texinfo-master-menu
with just C-u is still useful and much less problematic.
I decided not to remove the code that updates the @node lines
entirely, since texinfo-update-node could still be useful to experts
in very specialized use cases.
I also added to the doc strings of relevant commands a note about
non-support of multi-file Texinfo manuals, and a reference to
texinfo-multiple-files-update, which does.
I hope this makes the situation quite a bit better.
next prev parent reply other threads:[~2011-12-10 10:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 9:20 texinfo-master-menu and emacs.texi Roland Winkler
2011-12-07 9:57 ` Leo
2011-12-07 14:30 ` Roland Winkler
2011-12-07 13:19 ` Eli Zaretskii
2011-12-07 14:08 ` Roland Winkler
2011-12-08 6:46 ` Eli Zaretskii
2011-12-08 19:04 ` Roland Winkler
2011-12-10 11:01 ` Eli Zaretskii
2011-12-07 17:57 ` Glenn Morris
2011-12-07 19:26 ` Roland Winkler
2011-12-07 20:43 ` bug#2975: " 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
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 [this message]
2011-12-09 7:30 ` Eli Zaretskii
2011-12-08 19:33 ` Eli Zaretskii
2011-12-07 22:08 ` Roland Winkler
2011-12-07 22:13 ` Karl Berry
2011-12-10 12:42 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83borgn18a.fsf@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.