From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Babel] No output returned if just one command is failing
Date: Thu, 02 Dec 2010 21:34:27 +0100 [thread overview]
Message-ID: <80bp53ud64.fsf@missioncriticalit.com> (raw)
In-Reply-To: 87fwug9r8y.fsf@gmail.com
Hi Eric,
"Eric Schulte" wrote:
> You both make good points in favor of this behavior, and I had no idea
> this would be as easy as Dan's patch below, I was thinking that some
> sort of intermediate results return would be required.
>
> I would be open to either of Dan's suggested changes
> 1. return partial results for ":results output"
> 2. return partial results controlled by some new header argument
>
> I am worried by the prospect of partial results being used by another
> code block in chained code block execution. Perhaps some special care
> should be taken to ensure that this will not happen, or perhaps this
> should happen only in case two above where the user has explicitly
> specified that partial results are OK.
As I just expressed it, I would vote for "show the results as they are", and
"as they would be in a terminal". No special header needed, in my current view
of the Babel world.
In fact, I find the words "partial results" to be rather negative. They just
are the results a terminal would display: they're *all the available results*
that the block can generate in its execution context.
Best regards,
Seb
PS- I wanna repeat I may be proven wrong. Maybe I don't think (yet?) at all
impacts such a decision may have!
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-12-02 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 9:25 [Babel] No output returned if just one command is failing Sébastien Vauban
2010-12-01 14:29 ` Eric Schulte
2010-12-01 15:25 ` Sébastien Vauban
2010-12-02 10:03 ` Sébastien Vauban
2010-12-02 13:10 ` Dan Davison
2010-12-02 14:35 ` Eric Schulte
2010-12-02 20:34 ` Sébastien Vauban [this message]
2010-12-02 15:43 ` Sébastien Vauban
2010-12-02 18:02 ` Dan Davison
2010-12-02 20:27 ` Sébastien 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=80bp53ud64.fsf@missioncriticalit.com \
--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).