From: Marco Baringer <empb@bese.it>
Cc: emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: *.el files
Date: 09 Sep 2002 18:28:04 +0200 [thread overview]
Message-ID: <m2u1kzw2jv.fsf@bese.it> (raw)
In-Reply-To: <Pine.LNX.4.44.0209091546400.6121-100000@laptop.rkc>
Raimund.Kohl@freenet.de writes:
> Thank you very much, kai. Is there a special reason for using requite
> instead of load?
require will load the file (not really, but see the docs for require
for the gory details) only if it has not already been loaded, load
will always load it. in your .emacs it's not a big difference since
that only gets loaded once, but the convention is to use require
everywhere.
--
-Marco
Ring the bells that still can ring.
Forget your perfect offering.
There is a crack in everything.
That's how the light gets in.
-Leonard Cohen
next prev parent reply other threads:[~2002-09-09 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1031561802.29468.help-gnu-emacs@gnu.org>
2002-09-09 11:26 ` *.el files Kai Großjohann
2002-09-09 13:48 ` Raimund.Kohl
2002-09-09 16:28 ` Marco Baringer [this message]
2002-09-09 11:37 ` Jonas Steverud
2002-09-09 17:49 ` kgold
2002-09-09 8:51 Raimund.Kohl
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=m2u1kzw2jv.fsf@bese.it \
--to=empb@bese.it \
--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).