From: Andreas Politz <politza@fh-trier.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Getting Info to find extra pkgs not in normal path
Date: Tue, 09 Dec 2008 23:37:38 +0100 [thread overview]
Message-ID: <1228862325.415863@arno.fh-trier.de> (raw)
In-Reply-To: <mailman.2373.1228856474.26697.help-gnu-emacs@gnu.org>
Harry Putnam wrote:
> Andreas Politz <politza@fh-trier.de> writes:
>
>> It's there but not in the 'dir' file :
>>
>> (info "stumpwm")
>>
>> dir files will be merged by emacs, so you can create
>> one for your local additions. Probably by copying the
>> systems one from /usr/share/info/dir or wherever, delete
>> all entries after '* Menu:' and put in your own.
>>
>> (info "(texinfo)Other Info Directories")
>
> That section shows several ways to do it, but I find at least two of
> them don't seem to work for me... probably something I'm doing wrong.
>
> Before posting here about it I had tried to extend INFOPATH in my
> ~/.bashrc file like this:
>
> grep INFO ~/.bashrc
> INFOPATH=$INFOPATH:/usr/local/src/stumpwm:/usr/local/gnus/texi
>
> The Stand Alone info reader finds stumpwm but emacs does not
Eval (info "stumpwm") ,I am shure it'll work.
>
> Using the approach of adding my own dir file. (inlined below) at
> /usr/local/info/dir, inside a freshly started emacs
>
> `C-h i m stumpwm' fails
>
> My attempt appears to follow the example given:
> `
> * Test: (/home/bob/info/info-test). Bob's own test file. '
>
> On the stumpwm line shown here the address ends in the top level
> directory. The info file is directly under there. I also tried (not
> shown here) by putting the complete file name:
>
> (/usr/local/src/stumpwm/stumpwm.info)
>
> Do you see something wrong in both or either of my attempts (including
> the INFO path approach?
>
> cat /usr/local/info/dir
>
> Local info files (updates by user reader)
>
> * Stumpwm: (/usr/local/src/stumpwm/stumpwm.info). stump manual.
>
The dir file has to have a special header format. Just copy the systems one
into a directory in INFOPATH, erase everything afer '*Menu ' and put in
your own stuff.
-ap
next prev parent reply other threads:[~2008-12-09 22:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2336.1228841670.26697.help-gnu-emacs@gnu.org>
2008-12-09 17:35 ` Getting Info to find extra pkgs not in normal path Andreas Politz
2008-12-09 21:00 ` Harry Putnam
[not found] ` <mailman.2373.1228856474.26697.help-gnu-emacs@gnu.org>
2008-12-09 22:37 ` Andreas Politz [this message]
2008-12-09 23:32 ` Peter Dyballa
2008-12-10 8:56 ` Harry Putnam
2008-12-12 9:15 ` StumpWM and Gnome Sébastien Vauban
2008-12-12 20:31 ` Andreas Politz
2008-12-12 20:58 ` Jay Belanger
2008-12-12 21:18 ` Dmitri Minaev
2008-12-12 22:10 ` Ted Zlatanov
2008-12-18 9:50 ` Sébastien Vauban
2008-12-18 13:30 ` David Hansen
[not found] ` <mailman.3036.1229607504.26697.help-gnu-emacs@gnu.org>
2008-12-19 12:55 ` Sébastien Vauban
2008-12-19 16:15 ` henry atting
2008-12-29 10:50 ` Sébastien Vauban
2008-12-29 12:08 ` David Hansen
[not found] ` <mailman.3489.1230553403.26697.help-gnu-emacs@gnu.org>
2008-12-29 14:17 ` Sébastien Vauban
2008-12-09 16:54 Getting Info to find extra pkgs not in normal path Harry Putnam
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=1228862325.415863@arno.fh-trier.de \
--to=politza@fh-trier.de \
--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).