Re: [PATCH] Prefix CL symbols in ob-lisp.el

2025-03-07 Thread Héctor Galbis Sanchis
Owen is right. If the user is using any package that doesn't 'use-package' the "CL" package org will fail. I think the patch Owen provides is good. Just a little note on `org-babel-lisp-dir-fmt`. I think the symbol `*default-pathname-defaults*` should be `cl:*default-pathname-defaults*` too, since

ob-lisp patch

2025-03-02 Thread Héctor Galbis Sanchis
Hello Org: Over the last weeks I was talking with Ihor about `ob-lisp.el` and how it handles `verbatim` and multiple values returned by Common Lisp. I did a change where multiple values are now handled properly. In particular, returning multiple values works the same as returning a list. On the o

Re: Common Lisp weird Babel's results.

2025-02-24 Thread Héctor Galbis Sanchis
> I think that the code is already an improvement. Nice! > May you convert it into a proper patch against the latest main? Of course! I'll try to do it this weekend. El sáb, 22 feb 2025 a las 16:52, Ihor Radchenko () escribió: > Héctor Galbis Sanchis writes: > > >>

Re: Common Lisp weird Babel's results.

2025-02-09 Thread Héctor Galbis Sanchis
I guess I need to hack a bit org-babel-execute:lisp to suit my needs. Thaks for the answer anyway!! El dom, 9 feb 2025 a las 16:07, Ihor Radchenko () escribió: > Héctor Galbis Sanchis writes: > > > I noticed that some snippets are not printing the results as I expected. >

Common Lisp weird Babel's results.

2025-01-26 Thread Héctor Galbis Sanchis
Hello, I noticed that some snippets are not printing the results as I expected. >From this snippet: #+begin_src lisp :results value (values "Hello") #+end_src The results are: #+RESULTS: : Hello But it should be: #+RESULTS: : "Hello" I don’t know if this is the intended behaviour, but I t