From: Tim Johnson <tim@johnsons-web.com>
Subject: Re: No emacs info node
Date: Thu, 20 Apr 2006 16:57:26 -0000 [thread overview]
Message-ID: <slrne4fd65.e0e.tim@linus.johnson.com> (raw)
In-Reply-To: e27s03$vth$1@quimby.gnus.org
On 2006-04-20, Sven Urbanski <inf8237@fh-wedel.de> wrote:
> Eli Zaretskii wrote:
> I added two lines to this file (dir):
> "* gcc: (gcc). the gnu compiler
>
> 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 ?
I've had the same experience. On my box (RH 9)
usr/share/info is a symlink for /etc/info-dir.
I suspect the 'absence' of the emacs node might have been a result of
a later info installation.
Anyway, I'm happy to report that I know have my info node for GNU
emacs.
cheers
tim
--
Tim Johnson <tim@johnsons-web.com>
http://www.alaska-internet-solutions.com
prev parent reply other threads:[~2006-04-20 16:57 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
2006-04-20 14:20 ` Eli Zaretskii
2006-04-20 16:57 ` Tim Johnson [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=slrne4fd65.e0e.tim@linus.johnson.com \
--to=tim@johnsons-web.com \
/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).