emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Paul Sexton <psexton@xnet.co.nz>
To: emacs-orgmode@gnu.org
Subject: [babel] By default, code blocks should not be evaluated during export
Date: Fri, 8 Apr 2011 04:23:26 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110408T055427-629@post.gmane.org> (raw)

The default value of `org-export-babel-evaluate' is t. 

Having just crashed my Emacs session 5 times in a row trying to get
a file containing a BEGIN_SRC emacs-lisp ... END_SRC *code example*
to export to HTML...

I strongly feel it should default to nil.

I also feel that "executable code block" and "quoted code example that I would
like to display/export with pretty syntax highlighting" are two very different
concepts, and should have different block names.

eg #+BEGIN_EXEC for the executable blocks?
or allow an argument to example blocks, eg "#+BEGIN_EXAMPLE python" ?


             reply	other threads:[~2011-04-08  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08  4:23 Paul Sexton [this message]
2011-04-08  6:56 ` Rainer M Krug
2011-04-08 13:50 ` Eric Schulte
2011-04-08 15:28   ` Nick Dokos

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=loom.20110408T055427-629@post.gmane.org \
    --to=psexton@xnet.co.nz \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: [babel] By default, code blocks should not be evaluated during export' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).