From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: info-emacs-manual?
Date: Sat, 05 Feb 2022 09:09:59 +0200 [thread overview]
Message-ID: <837da93i2g.fsf@gnu.org> (raw)
In-Reply-To: <875ypuvdqd.fsf@t14.reltub.ca> (message from Leo Butler on Fri, 04 Feb 2022 09:43:54 -0600)
> From: Leo Butler <leo.butler@umanitoba.ca>
> Date: Fri, 04 Feb 2022 09:43:54 -0600
>
> After an
> apt-get update && apt-get dist-upgrade
> a few weeks ago, I have found the emacs manual is missing for the top
> info directory. That is,
>
> C-h i d m emacs RET
>
> doesn't send me to the emacs manual (I get a completion list,
> instead). And, sure enough, Emacs is missing from the menu.
>
> However
>
> M-x info-emacs-manual RET
>
> sends me to the manual.
>
> Is this expected behaviour?
It is the expected behavior if your /usr/share/info/DIR file doesn't
mention the Emacs manual. Which probably means no one run the
'install-info' command when the Emacs manuals were installed on your
system. "M-x info-emacs-manual" loads the Emacs Info manual directly,
bypassing the DIR menu, so it does work as soon as the manual is
available on your system.
Bottom line, you should investigate what is the source of the DIR file
and how it is updated when you install manuals.
prev parent reply other threads:[~2022-02-05 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 15:43 info-emacs-manual? Leo Butler
2022-02-04 15:57 ` info-emacs-manual? Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 16:46 ` info-emacs-manual? Jean Louis
2022-02-04 17:27 ` info-emacs-manual? Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 17:48 ` info-emacs-manual? Jean Louis
2022-02-04 20:07 ` info-emacs-manual? Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 20:36 ` info-emacs-manual? Leo Butler
2022-02-05 7:09 ` Eli Zaretskii [this message]
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=837da93i2g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).