From: Bernt Hansen <firstname.lastname@example.org> To: Nicolas Goaziou <email@example.com> Cc: firstname.lastname@example.org Subject: Re: New exporter - publishing org files doesn't include :tangle Date: Thu, 25 Apr 2013 23:15:47 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Nicolas Goaziou's message of "Wed, 24 Apr 2013 16:27:35 +0200") Nicolas Goaziou <email@example.com> writes: > Hello, > > Bernt Hansen <firstname.lastname@example.org> 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 > > > Regards, Hi Nick, So far my attempts using this workaround have failed and I can't get :tangle in my exported org file. I think I also would prefer to have the :exports value in the .org source as well so it's a true representation of the source. I'll give this another try again later. Regards, Bernt
next prev parent reply other threads:[~2013-04-26 3:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-24 14:17 Bernt Hansen 2013-04-24 14:27 ` Nicolas Goaziou 2013-04-24 14:52 ` Bernt Hansen 2013-04-24 14:53 ` Bernt Hansen 2013-04-26 3:15 ` Bernt Hansen [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: New exporter - publishing org files doesn'\''t include :tangle' \ /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
Code repositories for project(s) associated with this 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).