From: Fredrik Bulow <kaliumfredrik@gmail.com>
Subject: Re: No emacs info node
Date: Thu, 20 Apr 2006 10:59:02 +1000 [thread overview]
Message-ID: <877j5luko9.fsf@gmail.com> (raw)
In-Reply-To: slrne4crfj.9ks.tim@linus.johnson.com
Tim Johnson <tim@johnsons-web.com> writes:
> Using 21.4.1 on linux.
> No 'info' node for emacs is available.
> Example:
> c-h i memacs RET gives me [no match]
>
> the shell command: locate /info/emacs | more
> seems to indicate that emacs info files are at
>
> /usr/share/info
> and
> /usr/local/info/
>
> I've set INFOPATH as follows in .bashrc
> export INFOPATH="/usr/local/info:/usr/share/info"
> echo $INFOPATH from both shell and from emacs shell command
> confirms this path value.
>
> And here's the puzzling thing:
> 1)eval-expression (info "emacs") gives me the node.
> 2)calling `info emacs' from shell gives me the node
> as a standalone feature.
Hi Tim.
What happens if you evaluate (info), does that take you to the main
info page? What happens when you hit C-h k C-h i ? I get the message:
C-h i runs the command info
which is an interactive compiled Lisp function in `info'.
(info &optional FILE)
where `info' takes me to the file
/usr/share/emacs/21.4/lisp/info.el
Which Linux distro are you using? I'm using Ubuntu Breezy and the same
emacs version as you do and I didn't have to fiddle with the infopath
shell variable at all (in fact the variable is unset and echo
$INFOPATH gives a blank line) and my info pages works fine.
Hope any of this was usefull to you and good luck!
/Fredrik
next prev parent reply other threads:[~2006-04-20 0:59 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 [this message]
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
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=877j5luko9.fsf@gmail.com \
--to=kaliumfredrik@gmail.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).