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 16:04:58 +0200 [thread overview]
Message-ID: <80sjmz7hf9.fsf@somewhere.org> (raw)
In-Reply-To: CAGhLh6Ej_=+C_RgpZWiJ6cTWaB-QHKuMq1nVnssBaG=Je19vxg@mail.gmail.com
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...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-10-11 14:04 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 [this message]
2011-10-11 16:01 ` Burton Samograd
2011-10-11 16:52 ` Sebastien Vauban
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:
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=80sjmz7hf9.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.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).