From: Paul Sexton <psexton@xnet.co.nz>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] some nasty bugs with PROPERTIES drawers
Date: Tue, 31 Aug 2010 18:49:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20100831T204205-554@post.gmane.org> (raw)
In-Reply-To: 87iq2qix1l.wl%dmaus@ictsoc.de
David Maus <dmaus <at> ictsoc.de> writes:
> I cannot reproduce this wiht Org-mode version 7.01trans (pulled
> yesterday) on GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version
> 2.20.0) of 2010-08-14 on raven, modified by Debian
There is a documentation file, README.org, that accompanies org-drill.
It can be downloaded at:
http://bitbucket.org/eeeickythump/org-drill/src/tip/README.org
The quoted emacs lisp example occurs near the end of the file. As is, it
exports to HTML (C-c C-e h) successfully for me, but if I change
BEGIN_EXAMPLE/END_EXAMPLE to BEGIN_SRC/END_SRC for that block, it
reproduces the bug.
> >PS: I also realised that I was confused regarding how to get a syntax-
> >highlighted block of "example source code" into an org document, as
> >BEGIN_SRC appears to execute the code by default, which was not what
> >I wanted.
>
> No, at least not for Elisp. What is your assumption of Org mode
> executing source blocks based on?
>
My assumption is based on reading the manual. I couldn't find clearly stated
anywhere exactly what BEGIN_SRC blocks do by default during export, and there
are ":eval never" and "eval query" headline option, implying that these are not
the default behaviours. But perhaps I read it wrong.
Paul
next prev parent reply other threads:[~2010-08-31 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 3:13 [BUG] some nasty bugs with PROPERTIES drawers Paul Sexton
2010-08-31 7:28 ` Carsten Dominik
2010-08-31 16:09 ` David Maus
2010-08-31 18:49 ` Paul Sexton [this message]
2010-08-31 18:55 ` Erik Iverson
2010-08-31 19:05 ` Paul Sexton
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=loom.20100831T204205-554@post.gmane.org \
--to=psexton@xnet.co.nz \
--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).