Am Sa., 31. Dez. 2022 um 11:19 Uhr schrieb Marc Nieper-Wißkirchen <m...@nieper-wisskirchen.de>: > > Am Sa., 31. Dez. 2022 um 11:09 Uhr schrieb Marc Nieper-Wißkirchen > <m...@nieper-wisskirchen.de>: > > > > Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko > > <yanta...@posteo.net>: > > > > > > Marc Nieper-Wißkirchen <m...@nieper-wisskirchen.de> writes:
[...] > > > It is not what we usually do in Org babel. If blocks execution > > > fails, we display the error in separate buffer and still return the > > > output available before error has been thrown. See `org-babel-eval' and > > > `org-babel-eval-error-notify'. > > > > I will take a look. > > Hmmm... `org-babel-eval-error-notify' assumes that the code was > evaluated by running an external script. In the case of the Geiser > interface to Scheme, the concept of an exit code does not make any > sense. Please find attached a version that does not signal an Elisp user error, but calls `org-babel-eval-error-notify' instead. To get rid of the display of the arbitrary error code, could we modify `org-babel-eval-error-notify' so that nothing is displayed about an error if the error code is `nil'?
ob-scheme.el
Description: Binary data
