Re: Emacs mode can't run pil

. . . yes, sessions make perfect sense, but I thought sessions was an advanced feature for only some of the "elite" languages, i.e., so many of the babel languages don't support sessions. Still, I should have known to try. . . Now, why would trying to run picolisp (org-mode or picolisp-mode)

Re: Emacs mode can't run pil

Lawrence Bottorff writes: Hi Lawrence, [just for the protocoll, I send you the identical answer on the org-mode mailing list already]. > I'm looking at picolisp -- and wondering how it works, or better, why it > doesn't really work work with babel. First problem, I couldn't

Re: Emacs mode can't run pil

Nothing new; I've tried all that. Yes, *some* of the examples in https://github.com/tj64/ob-picolisp work. But again, the picolisp tutorial example #+BEGIN_SRC picolisp # call the 'MD5' function from 'libcrypto.so' (let Str "The quick brown fox jumped over the lazy dog's back" (pack

Re: Emacs mode can't run pil

As far as picolisp running in Org mode is concerned: ** 1. I tried the following code in org babel and they show perfect results as shown in ob-picolisp-more-tests.org given on https://github.com/tj64/ob-picolisp. *** Example 1 #+begin_src picolisp :results value html (load

Re: Emacs mode can't run pil

I tracked it down to something totally bizarre: Starting emacs GUI (I'm on Ubuntu + Gnome) from a task bar button with the command emacsclient -c -a '' (that's two single quotes) was the problem, i.e., using the emacs daemon. However, changing the task bar button to emacs --daemon then

Re: Emacs mode can't run pil

Hi Lawrence, Check: 1. If pil is running correctly in shell from inside Emacs. 2. If you added Picolisp in .emacs file in (org-babel-do-load-languages 'org-babel-load-languages '((picolisp . t))) On 2/21/18, Lawrence Bottorff wrote: >

Emacs mode can't run pil

I'm getting either Searching for program: No such file or directory, pil or File already exists: /home/hercynian/.pil/editor-orig whenever I try to do `run-picolisp` in Emacs. I've got pil correctly set up: >which pil /home/me/opt/picoLisp/pil and the command-line pil works fine >pil :