Bozhidar Batsov
Bozhidar Batsov
> Does the default completion-at-point function work with Cider? Yeah, it does. This code is one of the oldest parts of CIDER and has seen minimal changes in the past...
I see. So basically we need some `cider-completion-try-completion` function alongside the existing one. I guess I'll also have to check what are the benefits/use-cases of all the params we've suppressed...
Btw, I've also forgotten what's the difference between `completion-at-point-functions` and `completion-styles-alist`. Perhaps @dgutov can help by suggesting what'd be the appropriate changes.
I was mostly wondering if those completion styles have anything to do with `company-mode`, but I guess I'll figure this out myself when I find a bit of time.
Looking at the surrounding code - this was some hack to enable fuzzy completion in `company-mode`: ```elisp (defun cider-company-unfiltered-candidates (string &rest _) "Return CIDER completion candidates for STRING as is,...
That's just a matter of setting `cider-jack-in-default` to `babashka`. Perhaps we can also add option to prompt for the REPL type to use in such cases.
@vlnn That's a simple solution as well, but it's a slippery slope to have a jack-in command for every possible Clojure runtime. I'm not saying we won't do it, but...
@didibus Technically speaking there's no "standard" `cider-jack-in` anymore. It's just an alias for `cider-jack-in-clj`. I renamed it when we originally introduced support for ClojureScript. But yeah - in general I...
I understand the concerns with the change, but that command is supposed to simply pretty-print a result and do nothing more (the behavior should be consistent with regular evaluation). The...