From: Ole Laursen <olau@hardworking.dk>
Subject: Re: alternative to (require ...)
Date: Tue, 24 Feb 2004 19:47:58 +0100 [thread overview]
Message-ID: <87k72c9uw1.fsf@bach.composers> (raw)
In-Reply-To: 20040224163251.5739e4cd@deasker
Sam Halliday <devnull@example.com> writes:
[...]
> but if this package is not installed on the system, emacs bails on
> loading the rest of my ~/.emacs file. this is quite annoying as i
> like to maintain a single ~/.emacs file and use it wherever i am
> using emacs.
I do the following in my .emacs:
(if (file-readable-p "~/.local-emacs")
(load "~/.local-emacs"))
Then I put the stuff that is specific for a particular site into
.local-emacs so that I can keep the .emacs files synchronised.
--
Ole Laursen
http://www.cs.auc.dk/~olau/
next prev parent reply other threads:[~2004-02-24 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 16:32 alternative to (require ...) Sam Halliday
2004-02-24 17:19 ` Eli Zaretskii
2004-02-24 17:21 ` Kevin Rodgers
2004-02-24 17:36 ` Reiner Steib
2004-02-24 17:40 ` David Kastrup
2004-02-24 18:47 ` Ole Laursen [this message]
2004-02-24 21:12 ` Jason Rumney
2004-02-24 22:41 ` Sam Halliday
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=87k72c9uw1.fsf@bach.composers \
--to=olau@hardworking.dk \
/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).