From: "Thomas S. Dye" <tsd@tsdye.com>
To: andrea <andrea.crotti.0@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Moving to babel the whole configuration
Date: Thu, 21 Jan 2010 07:43:17 -1000 [thread overview]
Message-ID: <FED1DB84-3982-45EF-8401-0505ADBD1B1C@tsdye.com> (raw)
In-Reply-To: <m13a1ztoqk.fsf@gmail.com>
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
next prev parent reply other threads:[~2010-01-21 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 16:19 [babel] Moving to babel the whole configuration andrea
2010-01-21 16:45 ` Dan Davison
2010-01-26 17:28 ` Manish
2010-01-26 18:31 ` Eric Schulte
2010-01-26 20:34 ` Dan Davison
2010-01-26 23:24 ` Thomas S. Dye
2010-01-27 4:15 ` Manish
2010-01-21 17:43 ` Thomas S. Dye [this message]
2010-01-22 16:14 ` Eric S Fraga
2010-01-22 18:53 ` Richard Riley
2010-01-22 20:44 ` Eric S Fraga
2010-01-22 20:46 ` Greg Newman
2010-01-25 17:25 ` Manish
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FED1DB84-3982-45EF-8401-0505ADBD1B1C@tsdye.com \
--to=tsd@tsdye.com \
--cc=andrea.crotti.0@gmail.com \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).