Hi Nicolas, 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. I'm using --8<---------------cut here---------------start------------->8--- :publishing-function (org-html-publish-to-html org-org-publish-to-org) --8<---------------cut here---------------end--------------->8--- Regards, Bernt
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
Regards,
--
Nicolas Goaziou
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
>
>
> Regards,
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
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
>
>
> 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
Hello,
Bernt Hansen <bernt@norang.ca> writes:
> 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.
There was a bug in org back-end: affiliated keywords were
removed. I fixed it. Does it solve your problem (using the workaround)?
Regards,
--
Nicolas Goaziou
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Bernt Hansen <bernt@norang.ca> writes:
>
>> 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.
>
> There was a bug in org back-end: affiliated keywords were
> removed. I fixed it. Does it solve your problem (using the workaround)?
Thanks!
I'll try again tonight and let you know.
-Bernt
Bernt Hansen <bernt@norang.ca> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> Hello,
>>
>> Bernt Hansen <bernt@norang.ca> writes:
>>
>>> 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.
>>
>> There was a bug in org back-end: affiliated keywords were
>> removed. I fixed it. Does it solve your problem (using the workaround)?
>
> Thanks!
>
> I'll try again tonight and let you know.
>
> -Bernt
Yes I think this now works. The :exports details are missing but it's
usable for generating a emacs.el file now from the document.
Thanks!
Bernt