emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: David Rogers <davidandrewrogers@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to customize the heading definition in org-mode
Date: Sun, 11 Nov 2012 22:42:02 -0300	[thread overview]
Message-ID: <50a053ed.07cf640a.5e9b.4239@mx.google.com> (raw)
In-Reply-To: <20121110075840.72c827cb@blackbox>

At Sat, 10 Nov 2012 07:58:40 -0800,
David Rogers wrote:

But for this specific need (organizing the Emacs configuration with
org-mode), there is really no need for changing the headline
definition. You instead change your Emacs configuration to 'real' org-mode
files with the actual configuration inside Emacs-lisp src blocks. This is
much more powerful. As Memnon Anon mentioned, you only need a minimal
configuration in your init.el file and the rest can go all in one or more
org files that you load with org-babel-load-file.

I have converted my configuration to an org-mode file a good time ago and I
can tell you it is VERY worth the time invested. You can benefit from all
org-mode features. What org-babel-load-file does is tangling all of the
Emacs-lisp src blocks (only emacs-lisp blocks) to an Emacs lisp file and
then load that file. The org-babel-load-file function is smart enough to
only tangle the org file if something has changed. Therefore the delay
caused by the tangle process only happens when you change something.

A bonus side effect of this tangling process is that you can disable a
whole part of your Emacs configuration easily simple by setting the
'TANGLE' property of a headline containing the source blocks you want to
disable to 'no'.


> On Sat, 10 Nov 2012 10:38:41 +0000 (UTC)
> Memnon Anon <gegendosenfleisch@googlemail.com> wrote:
> > Avner Moshkovitz <avnermoshkovitz@lighthausvci.com> writes:
> > > I looked for an equivalent to this in org-mode but couldn't find a
> > > way to customize the heading definition.
> > >
> > > Is there a way to do so?
> > 
> > AFAIK, the * is a fixed part of the org syntax and is not
> > customizable.
> Yes, there was a discussion here not so long ago - the result of the
> discussion was (and I'm only paraphrasing) "It's true there is no way to
> change it, and we're intentionally keeping it that way to prevent
> needless complexity in org-mode".
> -- 
> David

      reply	other threads:[~2012-11-12  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 20:57 How to customize the heading definition in org-mode Avner Moshkovitz
2012-11-10 10:38 ` Memnon Anon
2012-11-10 15:58   ` David Rogers
2012-11-12  1:42     ` Darlan Cavalcante Moreira [this message]

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:

  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=50a053ed.07cf640a.5e9b.4239@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=davidandrewrogers@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).