From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: Re: [babel] Moving to babel the whole configuration Date: Thu, 21 Jan 2010 07:43:17 -1000 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NY147-0000Ap-Fs for emacs-orgmode@gnu.org; Thu, 21 Jan 2010 12:43:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NY142-00005k-Cy for emacs-orgmode@gnu.org; Thu, 21 Jan 2010 12:43:31 -0500 Received: from [199.232.76.173] (port=46745 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NY142-00005c-6w for emacs-orgmode@gnu.org; Thu, 21 Jan 2010 12:43:26 -0500 Received: from outbound-mail-158.bluehost.com ([67.222.39.38]:57600) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1NY141-000773-OA for emacs-orgmode@gnu.org; Thu, 21 Jan 2010 12:43:26 -0500 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: andrea Cc: emacs-orgmode@gnu.org On Jan 21, 2010, at 6:19 AM, andrea wrote: > I'm really tempted to move all my emacs configuration in only one > big file. > This would also help me to make it more consistent and readable. > > But I'm afraid to mess up something, in theory I just need: > - a simple org and babel loader > - one big file containing everything > > But how is emacs behaving? > > For example the customization frame would be able to write on that > file? > > Other possible problems? > Hi Andrea, Have you seen the emacs starter kits? I've found Eric Schulte's starter kit to be very handy. After struggling with emacs configuration for decades I now have at least the illusion of control. The configuration is held in a series of org files that hold emacs-lisp code blocks, which are tangled to produce the .el file that emacs expects. Each of my code chunks resides under its own org-mode heading, replete with notes, links, etc. It is kind of like a literate .emacs program. hth, Tom