Not used to the workflow on mailing lists but here is a second patch to
address that issue:
On Fri, Mar 7, 2025 at 6:01 PM Owen Radcliffe wrote:
> Yes, definitely prefix the special var too, thank you.
>
> On Fri, Mar 7, 2025 at 13:51 Héctor Galbis Sanchis <
> hectometrocua
gt;
> 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 it is also from the
> "CL" package.
>
>
> El vie, 7 mar 2025 a
The use of Coalton can be considered a contrived example, although
important to some people, but symbols not being prefixed assumes that users
are in packages that (:use :cl) and don't shadow anything important.
On Thu, Mar 6, 2025 at 13:58 Ihor Radchenko wrote:
> Owen Radcliffe
Symbols exported by the common-lisp package should be explicitly prefixed
so that users aren't required to be in a package that uses it. Currently
this is a problem if I want to use org-babel to evaluate Coalton code, but
I'm sure there are other cases where people want to evaluate code outside
of
