From: rustom <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: An alternative to a monolithic ~/.emacs init file
Date: 12 Nov 2007 17:22:50 -0800 [thread overview]
Message-ID: <1194790531.959978.297160@e34g2000pro.googlegroups.com> (raw)
In-Reply-To: <mailman.3247.1194750639.18990.help-gnu-emacs@gnu.org>
On Nov 10, 10:13 pm, Tom Tromey <t...@tromey.com> wrote:
>
> ELPA works this way, more or less. It isn't as simple as "drop in some elisp and work"
Thanks Tom. I checked out elpa and also install-elisp. Considering we
are living in the age of SOA -- think of the success of things like
apt in the linux world or eggs in python gems in ruby -- I suppose
its the in thing to be able to directly install an elisp file from a
web archive.
What I am looking for is something different:
- I have a bunch of my own customizations and autoloads rather than
ready made packages
- I of course want to autoload n rather than load n (for large n)
- The customize generated stuff only makes it much worse and more
monolithic.
- The .emacs file tends to become a kitchen sink kind of mess.
All this is not merely a question of aesthetics -- I like to sell
emacs to people but if I show a typical .emacs people would just run
away.
Note Francisco's solution does not separate out the autoload time from
the load time -- the basic problem as I see it.
So I am looking at an approach to distributing this kitchen
sink .emacs across different 'drawers' , each drawer (folder)
containing
1. autoloads loaded at emacs start time
2. customizations 'hooked' to the feature. [Admission: I dont
understand customizations very well]
3. the feature itself (This is usually absent because its a standard
mode in a standard place like cc-mode or python-mode etc)
I could of course write this infrastructure myself but I would be very
surprised if it had not already been written many times over before.
next prev parent reply other threads:[~2007-11-13 1:22 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 ` An alternative to a monolithic ~/.emacs init file rustom
2007-11-08 13:08 ` 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 [this message]
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=1194790531.959978.297160@e34g2000pro.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.