unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
Subject: Re: accessing own info files
Date: 12 Jan 2003 17:28:05 +0100	[thread overview]
Message-ID: <m3ptr272p6.fsf@cicero.benny.turtle-trading.net> (raw)
In-Reply-To: 87y95qr0ae.fsf@antithese.de

Hi Michael,


Michael Below <mbelow@antithese.de> writes:
> [...] because I thought maybe those dir files are being
> merged. [...]

That's right.

> This changed the behaviour of info, but not as intended: I keep
> getting
> 
> Search Failed: "
> ^_"
> 
> whenever I call info.

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.


Hope this helps, benny

  reply	other threads:[~2003-01-12 16:28 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 [this message]
2003-01-13 22:10   ` Michael Below
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=m3ptr272p6.fsf@cicero.benny.turtle-trading.net \
    --to=benjamin.riefenstahl@epost.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).