DONE :results org should be org block
- State "DONE" from "PROPOSED"
- State "PROPOSED" from "REJECTED"
- State "REJECTED" from "PROPOSED"
This is done now, albeit motivated differently. See commits 2c33b2eb66 and 3d2dbf8604.
The reason that :results org
was introduced was to support
seamless insertion of results into an org-mode buffer. This
proposal would defeat that initial purpose. [Eric]
No, we already have :results raw
which is currently synonymous
with org
. [Dan]
Also, the idea of org source blocks in an org-mode document seems needlessly complex and contorted. Of course I could be missing something here. [Eric]
Org already supports org source blocks (e.g. line 50 org-src.el). And there's at least one clear use case for them, i.e. demonstrating, in HTML, what an org buffer looks like:
Test export
You're reading HTML at the moment, but this is what org looks like in your emacs buffer.
I admit that I don't know how often one will want to generate org
blocks using babel, but I think that to use org
as a synonym of
raw
is inconsistent with :results latex
, :results html
,
:results code
. [Dan]