From: Bernt Hansen <bernt@norang.ca>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New exporter - publishing org files doesn't include :tangle
Date: Wed, 24 Apr 2013 10:53:59 -0400 [thread overview]
Message-ID: <87sj2gq8s8.fsf@norang.ca> (raw)
In-Reply-To: <8738ug9f6w.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 24 Apr 2013 16:27:35 +0200")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Bernt Hansen <bernt@norang.ca> writes:
>
>> James Yuan noticed that the .org file that is published with my document
>> (http://doc.norang.ca/org-mode.org does not contain :tangle on any of
>> the source blocks.
>>
>> One of the uses of this document is to pull up the file and tangle it to
>> create an emacs configuration but this seems to be broken in 8.0.
>
> This is not directly related to the export framework.
>
> For some reason, Babel removes all properties from the opening string of
> a block when evaluated. IOW
>
> #+BEGIN_SRC emacs-lisp :exports code :tangle yes
> (+ 1 1)
> #+END_SRC
>
> becomes
>
> #+BEGIN_SRC emacs-lisp
> (+ 1 1)
> #+END_SRC
>
> One workaround is to add Babel properties on a #+header: affiliated
> keyword instead as
>
> #+header: :tangle yes
> #+BEGIN_SRC emacs-lisp :exports code
> (+ 1 1)
> #+END_SRC
>
> becomes
>
> #+header: :tangle yes
> #+BEGIN_SRC emacs-lisp
> (+ 1 1)
> #+END_SRC
Thanks,
I'll give that a try. I think this used to work but as long as I can
get the same behaviour with your workaround that's fine with me.
Regards,
Bernt
next prev parent reply other threads:[~2013-04-24 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 14:17 New exporter - publishing org files doesn't include :tangle Bernt Hansen
2013-04-24 14:27 ` Nicolas Goaziou
2013-04-24 14:52 ` Bernt Hansen
2013-04-24 14:53 ` Bernt Hansen [this message]
2013-04-26 3:15 ` Bernt Hansen
2013-04-26 13:57 ` Nicolas Goaziou
2013-04-26 14:12 ` Bernt Hansen
2013-04-26 23:04 ` Bernt Hansen
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=87sj2gq8s8.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).