[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [PATCH] ob-eval: display error fix
From: |
Ihor Radchenko |
Subject: |
Re: [O] [PATCH] ob-eval: display error fix |
Date: |
Fri, 14 Apr 2023 12:44:53 +0000 |
Andreas Gerler <baron@bundesbrandschatzamt.de> writes:
> * lisp/ob-eval.el: (org-babel-eval-error-notify): Display standard
> error only if command exits non zero.
>
> The problem is that sql connections might give warnings.
> Now the information is available in the *Org-Babel Error* buffer
> without displaying.
> If you need always display toggle org-babel-eval-error-display-notify.
>
I am looking at this again, and there seems to be no simple way to know
which babel backend is active when org-babel-eval is invoked.
I think that we can use a different approach to handle the problem with
sql connections:
1. Add a new optional parameter to org-babel-eval that will disable
error buffer completely or when the command exits with 0 exit code.
2. Modify org-babel-execute:sql (and maybe other backends) to pass some
header argument value to `org-babel-eval'.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [O] [PATCH] ob-eval: display error fix,
Ihor Radchenko <=