From: "András Major" <andras.g.major@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: babel: results switch (output vs. value) has no or wrong effect for sh source block [7.7 (release_7.7.107.g7a82)]
Date: Fri, 19 Aug 2011 18:52:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20110819T204348-795@post.gmane.org> (raw)
In-Reply-To: 87pqk1o39w.fsf@gmail.com
Hi Eric,
> If we did return the value of shell scripts then ":results value" would
> almost always simply return 0 (or possibly an error message). For this
> reason shell code blocks do not implement value returns, but rather will
> always collect results from STDOUT.
I think that this unnecessarily throws away potentially useful
functionality. Example: I want to fill a table with data such that
the value of a cell depends on whether a file (whose path is specified
by another cell, for instance) exists or not. This would be most
easily done using an sh block which returns a numeric exit code. I
don't see a reason for making clandestine exceptions to the rules in
the manual and strongly suggest that the output and value options be
honoured for every language.
In order not to break existing Org files, I would suggest that the
default choice between value and output (when not explicitly
specified) depend on the language. With this functionality, sh code
blocks that don't specify ":results output" will still work as they
did before.
András
next prev parent reply other threads:[~2011-08-19 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 6:36 Bug: babel: results switch (output vs. value) has no or wrong effect for sh source block [7.7 (release_7.7.107.g7a82)] Andras Major
2011-08-19 13:33 ` Eric Schulte
2011-08-19 18:52 ` András Major [this message]
2011-08-19 19:03 ` Achim Gratz
2011-08-19 19:38 ` Sebastien Vauban
2011-08-19 19:20 ` Sebastien Vauban
2011-08-19 22:46 ` Eric Schulte
2011-08-22 21:49 ` Michael Brand
2011-08-23 16:18 ` Achim Gratz
2011-08-23 17:10 ` Eric Schulte
2011-08-23 17:13 ` Eric Schulte
2011-08-29 19:17 ` Michael Brand
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=loom.20110819T204348-795@post.gmane.org \
--to=andras.g.major@gmail.com \
--cc=emacs-orgmode@gnu.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).