From: rustom <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: An alternative to a monolithic ~/.emacs init file
Date: Wed, 07 Nov 2007 17:13:57 -0000 [thread overview]
Message-ID: <1194455637.485972.177570@s15g2000prm.googlegroups.com> (raw)
In-Reply-To: <mailman.2759.1193756709.18990.help-gnu-emacs@gnu.org>
Sebastian Tennant wrote:
> My ~/.emacs reads like this:
>
> ;;; generate auto-autoloads.el in ~/elisp/dotemacs/
> (let ((generated-autoload-file "~/elisp/dotemacs/auto-autoloads.el")
> (backup-inhibited t))
> (apply 'update-directory-autoloads '("~/elisp/lib/"))
> (kill-buffer (file-name-nondirectory generated-autoload-file)))
>
> ;;; load dotemacs/*.el (including auto-autoloads.el)
> (mapc (lambda (f) (load f))
> (split-string
> (shell-command-to-string "find ~/elisp/dotemacs -name *.el")))
>
> That's it, essentially.
>
> With this arrangement, library functions I've written that I don't
> always want to load at startup, but I do want to have to hand, go in
> ~/elisp/lib, and customisations (and functions I do always want to load
> at startup) go in ~/elisp/dotemacs.
>
> I can put my customisations and functions in as many .el files as I like
> within their respective directories, making it much easier to organise
> things generally.
>
> And to ensure a library function is always to hand (but not loaded) I
> simply need to remember to include an autoload cookie (;;;###autoload)
> in the library file, and an autoload form will be dynamically
> constructed and called at startup, i.e., there's no longer any need to
> write autoload forms manually any more.
>
> It's a win-win is it not? It works for me.
>
> Sebastian
Could you please elaborate on how this works a little?
I did try to understand this by following the info/help:
update-directory-autoloads -> update-file-autoloads -> loaddefs.el ->
magic cookies
And by now I am quite lost.
I really would like to have a tiny little .emacs file and a bunch of
files and directories containing unrelated stuff
next parent reply other threads:[~2007-11-07 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2759.1193756709.18990.help-gnu-emacs@gnu.org>
2007-11-07 17:13 ` rustom [this message]
2007-11-08 13:08 ` An alternative to a monolithic ~/.emacs init file Sebastian Tennant
[not found] ` <mailman.3126.1194527313.18990.help-gnu-emacs@gnu.org>
2007-11-08 19:53 ` rustom
2007-11-09 14:18 ` Sebastian Tennant
[not found] ` <mailman.3180.1194617919.18990.help-gnu-emacs@gnu.org>
2007-11-10 12:18 ` rustom
2007-11-10 17:13 ` Tom Tromey
[not found] ` <mailman.3247.1194750639.18990.help-gnu-emacs@gnu.org>
2007-11-11 15:29 ` rustom
2007-11-12 21:56 ` Tim X
2007-11-13 4:21 ` rustom
2007-11-13 9:26 ` Tim X
2007-11-14 3:52 ` rustom
2007-11-13 1:22 ` rustom
2007-11-11 0:09 ` Francisco Miguel Colaço
2007-10-30 15:04 Sebastian Tennant
2007-10-30 20:30 ` Sebastian Tennant
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=1194455637.485972.177570@s15g2000prm.googlegroups.com \
--to=rustompmody@gmail.com \
--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.
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.