emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Put result output in different type of code block than original
Date: Tue, 11 Oct 2011 18:52:17 +0200	[thread overview]
Message-ID: <80zkh75v3y.fsf@somewhere.org> (raw)
In-Reply-To: 87zkh7qzz9.fsf@interalia.com

Hi Burton,

Burton Samograd wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Hi Rainer and Niels,
>> Rainer M Krug wrote:
>>> On Mon, Oct 10, 2011 at 5:44 PM, Niels Giesen <niels.giesen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>wrote:
>>>> Say I've got a sh code block invoking curl to some json api, is it possible
>>>> some way to specify that the format of the output when :results output code
>>>> is in a json code block and *not* a sh code block?
>> FYI, this is a need I also have, for example AWK outputting SQL code. There
>> has been some threads about this, but nothing is implemented so far in this
>> direction.
>>>> #+begin_src sh :results output code :exports both
>>>> curl
>>>> https://our-service.org/getstuff?username=dirk\&password=catsbrithday\&fmt=json
>>>> #+end_src
>>> Does
>>> #+begin_src sh :results output :exports both
>>> echo #+BEGIN_SRC json
>>> curl
>>> https://our-service.org/getstuff?username=dirk\&password=catsbrithday\&fmt=json
>>> echo #+END_SRC
>>> #+end_src
>>> help?
>> I like very much the idea of your workaround. Great thought!
>> Though, nope, it does not help the OP, because the echo lines don't output
>> anything here, as # is the symbol to begin a comment (in shell scripts). So,
>> the first line simply outputs a blank line...
> Could you escape the comment character by using \#?

Yes, that does work as well (alternative to Eric's quoting method):

#+begin_src sh :results output raw :exports both
echo \#+BEGIN_SRC json
echo curl
echo https://our-service.org/getstuff?username=dirk\&password=catsbrithday\&fmt=json
echo \#+END_SRC

but my point was intended to be more general: this workaround may be difficult
to use for differnet languages to marry (my own need, in the past, was for AWK
outputting SQL + another I've forgotten about right now).

Anyway, this currently can be made to work, as shown.

Best regards,

PS- I was expecting that multiple evaluations of the code block would lead to
    multiple results blocks, because of the raw specifier. It's not the case.
    Is is perfectly normal and explainable, or a corner case which favors --
    in this case -- this workaround?

Sebastien Vauban

  reply	other threads:[~2011-10-11 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 15:44 Put result output in different type of code block than original Niels Giesen
2011-10-11  8:55 ` Rasmus Pank Roulund
2011-10-11  9:06 ` Rainer M Krug
2011-10-11 14:04   ` Sebastien Vauban
2011-10-11 16:01     ` Burton Samograd
2011-10-11 16:52       ` Sebastien Vauban [this message]
2011-10-11 20:55         ` Niels Giesen
2011-10-11 14:32 ` Eric Schulte

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:

  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=80zkh75v3y.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* 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


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).