Bastien <b...@gnu.org> writes:
> Daniel Kraus <dan...@kraus.my> writes: >> I would set it to (and (executable-find "bb") 'babashka) so it's still nil >> when babashka is installed? > (You mean "not installed", right?) Of course. >> Or we could even test more available backends like >> >> (cond >> ((executable-find "bb") 'babashka) >> ((executable-find "nbb") 'nbb) >> ((featurep 'cider) 'cider) >> ((featurep 'inf-clojure) 'inf-clojure) >> ((featurep 'slime) 'slime)) >> >> Or is that too much "magic" in that on some systems the default is bb >> and in others it's cider etc? > > I think this is acceptable magic: perhaps we should first check what > is done in other Babel languages and align with their level of magic > for guessing the correct executable -- but I suspect Clojure is a bit > special here, in that it has a lot of different options. I looked around a bit but couldn't find another babel package with a similar problems, i.e. that some backends are completely different and not just changing the name of the executable. 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. Cheers, Daniel
