From: Jay Kerns <gjkernsysu@gmail.com>
To: shripad sinari <shripad.sinari@gmail.com>
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Syntax of Org Babel ":results" header argument
Date: Fri, 15 Mar 2013 14:47:43 -0400 [thread overview]
Message-ID: <CAFiLVrYRC_ks00r_ZciZANRrmH0h3eV2j6k5uJ=2dw3a5ZjswQ@mail.gmail.com> (raw)
In-Reply-To: <CAA_SOTbe7fjDdqSqmn528VYV5tvd8Ne9=QuhAb8gUoa3+aaKaA@mail.gmail.com>
Greetings,
On Fri, Mar 15, 2013 at 1:30 PM, shripad sinari
<shripad.sinari@gmail.com> wrote:
[snip]
I am happy with the current behavior, but
that isn't to say it couldn't possibly be improved or that I
disagree with Sebastien's suggestions. It did take me quite some
time to figure out what the heck was going on with it all, but
now that I know, I like it a lot.
Few comments:
- :results graphics makes the list even longer, yes? :-) I'm not
sure that every language supports it and I don't believe it's
currently in the manual. And I don't think it directly affects
what Sebastien is asking about.
- Out of the myriad combinations, I only use a few regularly.
- I hope that a change, if any, would be mindful of
brevity. Particularly with inline src blocks, it is much
shorter to write
: SRC_foo[:results value scalar raw append]{blah}
than it is to write
: SRC_foo[:results_collect value :results_type scalar
:results_handling append :results_wrapper raw]{blah}
(or however it would be decided to handle that).
--
Jay
next prev parent reply other threads:[~2013-03-15 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 11:55 Syntax of Org Babel results Sebastien Vauban
2013-03-15 9:54 ` Syntax of Org Babel ":results" header argument Sebastien Vauban
2013-03-15 11:41 ` Eric S Fraga
2013-03-15 17:30 ` shripad sinari
2013-03-15 18:47 ` Jay Kerns [this message]
2013-03-17 8:30 ` Bastien
2013-03-17 21:31 ` Eric Schulte
2013-03-17 23:22 ` Thomas S. Dye
2013-03-18 8:27 ` Andreas Leha
2013-03-18 20:06 ` Sebastien Vauban
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='CAFiLVrYRC_ks00r_ZciZANRrmH0h3eV2j6k5uJ=2dw3a5ZjswQ@mail.gmail.com' \
--to=gjkernsysu@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=shripad.sinari@gmail.com \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).