From: Michael Below <mbelow@antithese.de>
Subject: Re: accessing own info files
Date: Mon, 13 Jan 2003 23:10:22 +0100 [thread overview]
Message-ID: <873cnwwvjl.fsf@antithese.de> (raw)
In-Reply-To: m3ptr272p6.fsf@cicero.benny.turtle-trading.net
Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de> writes:
> The easiest (for me) is just to create "dir" files from a command-line
> with install-info:
>
> $ install-info /usr/info/as.info /tmp/dir
>
> on my machine will create a dir file in /tmp with a link to the GNU
> assembler.
>
> The command install-info is documented in the texinfo documentation in
> the node (texinfo)Invoking install-info.
Hmmm... I am a Debian user, which is generally a good thing, but in
this case it makes things less easy: Debian has got an own version of
install-info, coming with dpkg.
Now I tried:
~ $/usr/sbin/install-info --infodir=temp elisp/info/gnus
* Gnus: (gnus). The newsreader Gnus.
install-info: failed to lock dir for editing! Datei oder Verzeichnis nicht gefunden
~ $/usr/sbin/install-info --infodir=/home/mbelow/temp elisp/info/gnus
* Gnus: (gnus). The newsreader Gnus.
install-info: failed to lock dir for editing! Datei oder Verzeichnis nicht gefunden
~ $touch temp/dir
~ $/usr/sbin/install-info --infodir=/home/mbelow/temp elisp/info/gnus
* Gnus: (gnus). The newsreader Gnus.
(Datei oder Verzeichnis nicht gefunden means "file or directory not
found" in english)... I made a "dir" file using touch, and now
install-info did run for minutes with very high load, it looks like it
expected something else from the dir file. Adding an entry to my
experimental dir file worked smoothly, but it didn't make it more
readable for info...
Should I file a bug report against the Debian install-info? Should I
reinstall texinfo from sources? Or is there an easier solution?
Michael
--
Der hohe Anteil an Dienstreisen fällt auf.
Niklas Luhmann, Die Weltgesellschaft, ARSP 1971, 8
next prev parent reply other threads:[~2003-01-13 22:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 12:59 accessing own info files Michael Below
2003-01-12 16:28 ` Benjamin Riefenstahl
2003-01-13 22:10 ` Michael Below [this message]
2003-01-14 7:17 ` Kai Großjohann
2003-01-14 15:36 ` Benjamin Riefenstahl
2003-01-14 17:14 ` Kai Großjohann
2003-01-15 1:09 ` Peter S Galbraith
2003-01-15 18:39 ` Benjamin Riefenstahl
2003-01-16 11:11 ` Alfred M. Szmidt
[not found] ` <mailman.367.1042715506.21513.help-gnu-emacs@gnu.org>
2003-01-16 15:43 ` Kai Großjohann
2003-01-16 17:04 ` Alfred M. Szmidt
[not found] ` <mailman.388.1042737292.21513.help-gnu-emacs@gnu.org>
2003-01-16 20:01 ` Kai Großjohann
2003-01-17 11:42 ` Alfred M. Szmidt
2003-01-16 19:11 ` Michael Below
2003-01-17 11:40 ` Alfred M. Szmidt
2003-01-13 3:16 ` Galen Boyer
2003-01-14 13:48 ` solution for " Michael Below
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=873cnwwvjl.fsf@antithese.de \
--to=mbelow@antithese.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).