Am Sa., 7. Jan. 2023 um 08:44 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> >> Thanks!
> >> Note that your patch does not apply onto main.
> >
> > Rebased against the latest main. Please see the appended patch.
>
> Hmm.
>
Am Fr., 6. Jan. 2023 um 17:34 Uhr schrieb :
>
> On Fri, Jan 06, 2023 at 04:20:29PM +, Ihor Radchenko wrote:
> > Ihor Radchenko writes:
> >
> > > Marc Nieper-Wißkirchen writes:
> > > ...
> >
> > May someone forward my last email to Marc?
&g
under such an assignment in the past.)
Thanks,
Marc
Am Mo., 2. Jan. 2023 um 10:52 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Am Mo., 2. Jan. 2023 um 10:38 Uhr schrieb Ihor Radchenko
> :
> >
> > Marc Nieper-Wißkirchen writes:
> >
> > > Fixed.
> >
> >
Am Mo., 2. Jan. 2023 um 10:38 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > Fixed.
>
> Thanks!
> Note that your patch does not apply onto main.
Rebased against the latest main. Please see the appended patch.
>
> > -
Fixed.
Am So., 1. Jan. 2023 um 14:53 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > (defun org-babel-eval-error-notify (exit-code stderr)
> > - "Open a buffer to display STDERR and a message with the value of
> > EXIT-CODE."
> >
Done!
Am Sa., 31. Dez. 2022 um 14:24 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > Please find the patch file attached to this email.
>
> Thanks!
> I will give some general comments and leave the ob-scheme changes for
> Rudolf.
>
> >
Please find the patch file attached to this email.
Thank you,
Marc
Am Sa., 31. Dez. 2022 um 13:07 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > Please find attached a version that does not signal an Elisp user
> > error, but calls `org-babel-eval-
Am Sa., 31. Dez. 2022 um 11:19 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Am Sa., 31. Dez. 2022 um 11:09 Uhr schrieb Marc Nieper-Wißkirchen
> :
> >
> > Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko
> > :
> > >
> > > Marc Nieper-Wißkirc
Am Sa., 31. Dez. 2022 um 11:09 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko
> :
> >
> > Marc Nieper-Wißkirchen writes:
> >
> > > I have been talking to jao (from geiser). The following version of
>
Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > I have been talking to jao (from geiser). The following version of
> > ob-scheme.el signals an error when executing Scheme code blocks.
> > Besides two function decla
Hi,
I have a code block outputting mathematical LaTeX code as a result:
#+BEGIN_SRC ... :wrap equation*
#+END_SRC
The result looks like
#+RESULTS:
#+begin_equation*
#+end_equation*
As does not contain the surrounding
\begin{equation*}/\end{equation*}, I added the :wrap keyword.
Export to L
I have been talking to jao (from geiser). The following version of
ob-scheme.el signals an error when executing Scheme code blocks.
Besides two function declarations, the only change is in the function
org-babel-scheme-execute-with-geiser.
;;; ob-scheme.el --- Babel Functions for Scheme -*-
When I evaluate erroneous code of an Elisp code block like
#+BEGIN_SRC elisp
(x)
#+END_SRC
I see the error message ("Symbol's function definition is void: x") in
the minibuffer (and in the *Messages* buffer).
This is not the case with Scheme code blocks; evaluating the code block
#+BEGIN_SRC sc
13 matches
Mail list logo
