From: Greg Minshall <minshall@umich.edu>
To: "Berry, Charles" <ccberry@health.ucsd.edu>
Cc: James Powell <powellj@pdx.edu>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Bug: :session results in unfriendly error reporting
Date: Tue, 17 Aug 2021 08:02:12 +0300 [thread overview]
Message-ID: <1755618.1629176532@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Mon, 16 Aug 2021 18:25:37 +0000." <FC24C431-9095-4E05-ACD3-FB72BB73852D@health.ucsd.edu>
Charles,
being sympathetic with the idea of better error reporting, i'm curious
about the following.
> Right. But there is no error as far as babel is concerned. R has
> handled the condition. So there is nothing for babel to see/do.
...
> Running R in this fashion starts a fresh process which signals an
> error that babel can handle. I see no easy way to get sessions to
> sends signals that babel can process.
what is going on here? is the issue that in the no-session case, the R
process exits with a non-zero exit code, and that is how "babel" picks
up on it?
i put "babel" in quotes ("\"babel\"" :) above, because, in my simple
mind, babel isn't just the main bit that runs inside org/emacs, but also
some glue bits that run in the various languages' environments. things
like initializing variables, and harvesting results. so, might one not
argue that checking execution status, in a session environment, could
also be part of babel?
cheers, Greg
next prev parent reply other threads:[~2021-08-17 5:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 23:41 Bug: :session results in unfriendly error reporting James Powell
2021-08-16 18:25 ` Berry, Charles via General discussions about Org-mode.
2021-08-17 5:02 ` Greg Minshall [this message]
2021-08-17 6:23 ` Tim Cross
2021-08-17 7:44 ` Greg Minshall
2021-09-27 8:42 ` Bastien
2021-09-27 9:52 ` Greg Minshall
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=1755618.1629176532@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=ccberry@health.ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=powellj@pdx.edu \
/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).