emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
	Sebastien Vauban
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Subject: Re: [babel] Purpose of :results raw
Date: Sat, 20 Apr 2013 16:34:35 -0500	[thread overview]
Message-ID: <CA+M2ft9ZG4YErN_2MDqJF28fphN9fkpnf9DxwiefD_Zk7r11XA@mail.gmail.com> (raw)
In-Reply-To: <878v4ep362.fsf@gmail.com>



On Fri, Apr 19, 2013 at 5:27 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>
> Hello,
>
> "Sebastien Vauban"
> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> Now that ":results drawer" has been introduced, I wonder why we still have
>> ":results raw".
>>
>> As once stated in this ML:
>>
>>      The sole purpose of raw results is to allow inserting an headline (I mean
>>      a real headline, not comma protected) in the buffer, because headlines
>>      cannot be contained in anything else than headlines.
>>
>> But drawer does the same.
>
> What makes you think drawers do the same? Drawers cannot contain
> headlines.
>

But back to the original question, what does =:results raw=
accomplish? From my view, even if they *can* contain headlines, they
get exported twice, and re-running the code block just adds duplicate
output to whatever was already there. Consider this test file:

#+begin_src orgmode

* Heading

#+begin_src R :session r :results output raw :exports results

cat("* Heading2\n")
cat("This is some test text\n")

#+end_src

#+RESULTS:
* Heading2
This is some test text

#+begin_src R :session r :results output drawer :exports results

cat("* Heading3\n")
cat("This is some test text\n")

#+end_src

#+RESULTS:
:RESULTS:
* Heading3
This is some test text
:END:


* Heading 4

#+begin_src R :session r :results output drawer :exports results

cat("This is some test text\n")

#+end_src

#+RESULTS:
:RESULTS:
This is some test text
:END:

#+end_src

"** Heading2" gets exported twice, and the :RESULTS: and :END: drawer
property indicators are also being exported. Yes, I can delete the
=:results raw= output, but that's time consuming, especially as one
tweaks code and re-evaluates to check the results. One has to do this
every time not to flood the document with duplicate results.

See Eric Schulte's response here:
- http://lists.gnu.org/archive/html/emacs-orgmode/2012-08/msg01224.html

I was getting multiple instance with =:results output raw= and was
instructed to use =:results output org= for the very reason that it
would be able to discern the output and replace it upon subsequent
block evaluations.

Now consider this recent thread:
- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg70016.html

The gist of that long discussion is that =:results output org= was
replaced by =:results output drawer=, but it seems we haven't
recreated all of the existing functionality. There's another thread
out there in which for a while it was to be =:results output wrap=
and/or =:wrap org= in order to do something like this (output actual
Org-mode syntax from a code block and have it exported as if it was
actually written in the document).

There are instances where I'd like to generate numerous plots and then
create subheadings for the various iterations of my loops, so having
the ability to actual print "** Subheading" to a results block and
have it exported would be useful. Seems that =:results raw= is now the
only way to do that, and export only works if you delete whatever
results are down there already prior to doing so.

Let me know if there's another/better way.


Thanks,
John

>
> Regards,
>
> --
> Nicolas Goaziou
>
>

      parent reply	other threads:[~2013-04-20 21:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 22:11 [babel] Purpose of :results raw Sebastien Vauban
2013-04-19 22:27 ` Nicolas Goaziou
2013-04-20  7:14   ` Sebastien Vauban
2013-04-20 11:52     ` Nicolas Goaziou
     [not found]       ` <CAJcAo8uRp8xOk+_cZefMc8PBfMDywzARdkTyCR_FDuXCLjAnZA@mail.gmail.com>
2013-04-22  1:43         ` Samuel Wales
2013-04-20 21:34   ` John Hendy [this message]

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=CA+M2ft9ZG4YErN_2MDqJF28fphN9fkpnf9DxwiefD_Zk7r11XA@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=n.goaziou@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).