From: Sven Urbanski <inf8237@fh-wedel.de>
Subject: Re: No emacs info node
Date: Thu, 20 Apr 2006 13:39:10 +0200 [thread overview]
Message-ID: <e27s03$vth$1@quimby.gnus.org> (raw)
In-Reply-To: mailman.634.1145527664.9609.help-gnu-emacs@gnu.org
Eli Zaretskii wrote:
>> From: Sven Urbanski <inf8237@fh-wedel.de>
>> Date: Thu, 20 Apr 2006 09:50:47 +0200
>>
>> In fact, I think it's not an emacs problem. When I have a shell (no
>> emacs, just bash) and type
>> $ info emacs
>> I get the emacs info node. But typing
>> $ info
>> g emacs
>> I get: Cannot find node `emacs'.
>> It's the same with typing
>> mEmacs
>> I get:
>> Menu item: Emacs [No completions]
>
> One possible reason for this discrepancy is that the file named `dir'
> in your `info' directory doesn't include a menu entry for the Emacs
> manual. Can you verify that?
Yes, this is true.
I added two lines to this file (dir):
"* gcc: (gcc). the gnu compiler
* emacs: (emacs). gnu emacs
"
now everything's working as it should in bash _and_ in emacs.
Thanks for this hint!
But the file 'dir' is auto-generated, isn't it?
In other words: why did I have to add these lines ?
Sven
next prev parent reply other threads:[~2006-04-20 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 17:51 No emacs info node Tim Johnson
2006-04-20 0:59 ` Fredrik Bulow
2006-04-20 2:57 ` Tim Johnson
2006-04-20 4:10 ` Fredrik Bulow
2006-04-20 7:50 ` Sven Urbanski
2006-04-20 10:07 ` Eli Zaretskii
[not found] ` <mailman.634.1145527664.9609.help-gnu-emacs@gnu.org>
2006-04-20 11:39 ` Sven Urbanski [this message]
2006-04-20 14:20 ` Eli Zaretskii
2006-04-20 16:57 ` Tim Johnson
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='e27s03$vth$1@quimby.gnus.org' \
--to=inf8237@fh-wedel.de \
/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).