From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to install save-history.el in my home directory
Date: Mon, 24 Oct 2005 16:20:31 +0200 [thread overview]
Message-ID: <09bc8c74a5516beac5b374d467d42e0b@Web.DE> (raw)
In-Reply-To: <1130160374.8814.4.camel@localhost.localdomain>
Am 24.10.2005 um 15:26 schrieb Helfer Thomas:
> (require 'save-history)
>
You have require here, save-history.el should then have a provide
statement.
Does it work interactively to M-x load-library <RET> save-history
<RET>? If this succeeds then load-path is correct. Remember: you can
mark a region and invoke evaluate-region on it to extend load-path. And
you can check load-path's value too (C-h v with cursor on it).
And there's the *Messages* buffer too, but I think you already
discovered it ...
--
Greetings
Pete
Without vi there is only GNU Emacs
prev parent reply other threads:[~2005-10-24 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 13:26 How to install save-history.el in my home directory Helfer Thomas
2005-10-24 13:56 ` Peter Dyballa
2005-10-24 14:20 ` Peter Dyballa [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=09bc8c74a5516beac5b374d467d42e0b@Web.DE \
--to=peter_dyballa@web.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).