From: Michael Below <mbelow@antithese.de>
Subject: solution for accessing own info files
Date: Tue, 14 Jan 2003 14:48:04 +0100 [thread overview]
Message-ID: <877kd7267f.fsf@antithese.de> (raw)
In-Reply-To: 87y95qr0ae.fsf@antithese.de
Michael Below <mbelow@antithese.de> writes:
> As a next step, I tried making a "dir" file of my
> own in /home/mbelow/elisp/info , because I thought maybe those dir
> files are being merged. This changed the behaviour of info, but not as
> intended: I keep getting
>
> Search Failed: "
> ^_"
I found it (thanks to less): I had inserted the two characters caret
and underscore, but that's not what is meant by "^_" in the info
documentation, it has to be the single character I would describe as
C-_ in emacs notation. Using vim, I was able to insert that
character, and now everything is working as I wanted it to be...
Ciao
Michael
--
_Agricultural activity_ is the management by an enterprise of the
biological transformation of biological assets for sale, into
agricultural produce, or into additional biological assets. IAS 41,5
prev parent reply other threads:[~2003-01-14 13:48 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
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 ` Michael Below [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=877kd7267f.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).