all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Colin S. Miller <no-spam-thank-you@csmiller.demon.co.uk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: for loading own lisp functions, if some in separated files, automatically
Date: Wed, 15 Jul 2009 02:10:12 +0200	[thread overview]
Message-ID: <E4704F60-58E9-468C-850E-CEA7DF0E49AB@Web.DE> (raw)
In-Reply-To: <4a5d0f26$0$48241$14726298@news.sunsite.dk>


Am 15.07.2009 um 01:05 schrieb Colin S. Miller:

> You mean something like this?
> (loop for lib in (directory-files "~/my-emacs-packages/" 't "elc?$"  
> 't) do (load-library lib))


No (and also no to the updated version).

Add "~/my-emacs-packages" (or ~/.emacs.d etc., see documentation) to  
GNU Emacs' load-path. If your Elisp files have a provide statement  
you can require them (i.e., they get loaded when something they  
provide gets used). Otherwise load-library has to be used.

And of course I thought you would put a series of load statements  
into your init file to be able to comment or uncomment statements,  
i.e., to have control of what "gets used." Anyway, if the ELC files  
are tested and final versions, you can "load" them in a loop…

--
Greetings

   Pete

Perl—the only language that looks the same before and after RSA  
encryption.
				- Keith Bostic







      parent reply	other threads:[~2009-07-15  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 15:34 for loading own lisp functions, if some in separated files, automatically Erhy
2009-07-14  7:39 ` Peter Dyballa
2009-07-14 11:29 ` Abdullah Abdul Khadir
     [not found] ` <mailman.2466.1247557209.2239.help-gnu-emacs@gnu.org>
2009-07-14 17:42   ` Erhy
2009-07-14 23:05     ` Colin S. Miller
2009-07-14 23:16       ` Colin S. Miller
2009-07-15  0:10       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E4704F60-58E9-468C-850E-CEA7DF0E49AB@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=no-spam-thank-you@csmiller.demon.co.uk \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.