From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Cc: Bill Wohler <wohler@newt.com>, Reiner Steib <Reiner.Steib@gmx.de>,
Teodor Zlatanov <tzz@lifelogs.com>,
Michael Kifer <kifer@cs.stonybrook.edu>,
Jay Belanger <jay.p.belanger@gmail.com>,
Katsumi Yamaoka <yamaoka@jpl.org>,
Michael Albinus <michael.albinus@gmx.de>,
Carsten Dominik <carsten.dominik@gmail.com>,
Alan Mackenzie <acm@muc.de>, Karl Berry <karl@gnu.org>
Subject: @dircategory entries sync'ed with info/dir
Date: Fri, 18 Feb 2011 16:20:27 +0200 [thread overview]
Message-ID: <83oc69v2z8.fsf@gnu.org> (raw)
I've committed to the emacs-23 branch changes in almost all of the
manuals in doc/misc that synchronize their @dircategory directives
with the corresponding entries in the info/dir top-level menu. This
is so running install-info on the Emacs Info files does not cause
duplicate entries in the menu created by the Info readers from all the
`dir' files it finds on INFOPATH.
Some of the manuals' master copies are maintained outside of the Emacs
repository. I tried to CC all of them here. Please, when merging
future versions into the Emacs repository, be extra careful so as not
to lose these changes. Ideally, you should sync your master copies
with these changes now. Thanks in advance.
There's one problem left in this area that I'm unsure what to do
about, if at all. The @dircategory directive of info.texi says
"Texinfo documentation system", and I believe it is maintained as part
of the Texinfo package. The info/dir file that comes with Emacs puts
the corresponding menu entry at the very beginning (so that Info
newbies could see it), with no category at all. OTOH, changing the
@dircategory for info.texi would be frowned upon by the Texinfo
maintainers. So I didn't change it for now.
Karl, any suggestions?
Personally, I tend to think we could leave it alone: if someone runs
install-info on the Emacs Info manuals, she probably already has the
Texinfo manuals installed anyway, so the entry for `info' will end up
in that part, which is okay.
next reply other threads:[~2011-02-18 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 14:20 Eli Zaretskii [this message]
2011-02-18 15:23 ` @dircategory entries sync'ed with info/dir Michael Albinus
2011-02-18 15:30 ` Eli Zaretskii
2011-02-18 15:35 ` Michael Albinus
2011-02-18 18:55 ` Glenn Morris
2011-02-18 22:58 ` Michael Albinus
2011-02-18 23:17 ` Glenn Morris
2011-02-19 19:58 ` Michael Albinus
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=83oc69v2z8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Reiner.Steib@gmx.de \
--cc=acm@muc.de \
--cc=carsten.dominik@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jay.p.belanger@gmail.com \
--cc=karl@gnu.org \
--cc=kifer@cs.stonybrook.edu \
--cc=michael.albinus@gmx.de \
--cc=tzz@lifelogs.com \
--cc=wohler@newt.com \
--cc=yamaoka@jpl.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.