Daniel Kraus writes:
> Ihor Radchenko writes:
>
>> Daniel Kraus writes:
>>
>>> +(defcustom org-babel-clojure-backend (cond
>>> + ((executable-find "bb") 'babashka)
>>> + ((executable-find "nbb") 'nbb)
>>> +
Tim Cross writes:
> I think bb is a much better solution from a babel perspective and would
> love to see it as the default, even when you have both bb and cider
> installed.
I just installed the patch. So if you have `bb` in your path, ob-clojure
should use babashka as default and only fall b
Daniel Kraus writes:
> Ihor Radchenko writes:
>
>> Daniel Kraus writes:
>>
>>> +(defcustom org-babel-clojure-backend (cond
>>> + ((executable-find "bb") 'babashka)
>>> + ((executable-find "nbb") 'nbb)
>>> +
Daniel Kraus writes:
>> What if users have, say, cider installed and also babashka executable?
>> Will it be expected to use babashka?
>
> Yes. The only thing that makes me slightly hesitant is that e.g.
> someone doesn't have `bb` installed. Executes clojure source blocks
> which are then evalua
Ihor Radchenko writes:
> Daniel Kraus writes:
>
>> +(defcustom org-babel-clojure-backend (cond
>> + ((executable-find "bb") 'babashka)
>> + ((executable-find "nbb") 'nbb)
>> + ((featu
Daniel Kraus writes:
> Bastien writes:
>
>> Daniel Kraus writes:
>>
>>> I think I'll go with the big `cond` above to auto-detect what's
>>> installed. That's probably the best out-of-the-box experience.
>> Indeed, thank you!
>
> I would push the attached patch.
> +(defcustom org-babel-clojure-
Bastien writes:
> Daniel Kraus writes:
>
>> I think I'll go with the big `cond` above to auto-detect what's
>> installed. That's probably the best out-of-the-box experience.
> Indeed, thank you!
I would push the attached patch.
I'm not sure about the `:package-version` keyword in defcustom.
I
