Daniel Kraus <dan...@kraus.my> writes: > Bastien <b...@gnu.org> writes: > >> Daniel Kraus <dan...@kraus.my> 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-backend (cond > + ((executable-find "bb") 'babashka) > + ((executable-find "nbb") 'nbb) > + ((featurep 'cider) 'cider) > + ((featurep 'inf-clojure) 'inf-clojure) > + ((featurep 'slime) 'slime) > + (t nil)) What if users have, say, cider installed and also babashka executable? Will it be expected to use babashka? > I'm not sure about the `:package-version` keyword in defcustom. > I want to say that the default value changed. > Should I do it this way? Is `(Org . "9.6")` correct as it's unreleased? Yes. 9.6 is the next release - our main branch is labeled Org 9.6-pre. So, using 9.6 is correct. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
