From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: rustom Newsgroups: gmane.emacs.help Subject: Re: An alternative to a monolithic ~/.emacs init file Date: 12 Nov 2007 17:22:50 -0800 Organization: http://groups.google.com Message-ID: <1194790531.959978.297160@e34g2000pro.googlegroups.com> References: <1194455637.485972.177570@s15g2000prm.googlegroups.com> <1194544126.425679.261670@e9g2000prf.googlegroups.com> <1194697099.703581.205890@i38g2000prf.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: ger.gmane.org 1194918118 10686 80.91.229.12 (13 Nov 2007 01:41:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Nov 2007 01:41:58 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Nov 13 02:42:03 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Irkmu-0004tW-P7 for geh-help-gnu-emacs@m.gmane.org; Tue, 13 Nov 2007 02:42:00 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Irkme-0007R5-MF for geh-help-gnu-emacs@m.gmane.org; Mon, 12 Nov 2007 20:41:44 -0500 Original-Path: shelby.stanford.edu!headwall.stanford.edu!newsfeed.stanford.edu!postnews.google.com!e34g2000pro.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 38 Original-NNTP-Posting-Host: 59.95.33.144 Original-X-Trace: posting.google.com 1194916982 30150 127.0.0.1 (13 Nov 2007 01:23:02 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Tue, 13 Nov 2007 01:23:02 +0000 (UTC) In-Reply-To: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20070508 Iceweasel/2.0.0.4 (Debian-2.0.0.4-0etch1),gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: e34g2000pro.googlegroups.com; posting-host=59.95.33.144; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 Original-Xref: shelby.stanford.edu gnu.emacs.help:153734 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:49184 Archived-At: On Nov 10, 10:13 pm, Tom Tromey 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.