EmmanuelCharpentier

Adding the sole commit of the stale `wolfram` branch in a newbranch didn't change a thing... HTH,

One more data point : when called from an `org` source block, `jupyter-Wolfram-Language` *does* give an answer, which is *by default* formatted as an HTML *image* (!!!), but can be...

Okay. I'll fork your repo and have a look at this. Don't hold your breath : I never created a `melpa`-ready package, and may have a couple of false starts...

Put on the back burner : there seems to be two *currently active* APL implementations (Dyalog an Gnu APL), and Dyalog seems to have drifted to a different set of...

I have the same (non-)problem ; the illegac character may be `+` or `:`. No other symptom... HTH,

> Do you have a way to reproduce? Certainly : at every start of `gnu-apl` in a "fresh" emacs session, I get : ``` This is the gnu-apl-mode interactive buffer....

`:output-dir` is not currently listed as a supported header argument for Sage. It's a nice whishlist item, but *not* supported code... I suggest closing this issue.

Opening a Sage sessio` has other issues :my crrent practice is to open a Sage session from `emacs` prompt (`M-x run-sage`), *then* open my `.org` file. To be spruced up...

As of 9.7.beta8, this works : ```sage #+name: test2 #+begin_src sage :exports both :results file link :file test2.pdf plot(sin, (-pi, pi), figsize=4) #+end_src #+RESULTS: test2 [[file:test2.pdf]] ``` I sugest closing...

Can you access *Console* sagemath by typing `sage` at a terminal prompt ?