Bozhidar Batsov
Bozhidar Batsov
> Proper solution would be to run two nREPL servers with two separate sets of middleware. First one with Dirac middleware available for Dirac nREPL client(s) in Chrome. And second...
I assume you've added the documentation function just to be able to show the doc tooltips on completion, but for me it seems that using to show the javadoc about...
Btw, `documentation` doesn't seem to work properly with classes: ``` (compliment.core/documentation "String" *ns*) => "\n nil\n" ```
1 & 2 - Understood. 3 - not sure what the best return value would be. I guess it can be a list of fully qualified class names to be...
> Not sure I got you right on this one. Do you mean to show the fully qualified classname together with all method signatures of this class? Yeah, that'd be...
We've implemented the Javadoc handling (using the JDK's built-in javadoc parser) in `cider-nrepl`. You might refer to the code there if it's something you'd like to add to `compliment`.
@FiV0 You might consider taking a stab at this one as well.
Yeah, I think that's the line. nREPL basically just delegates to Clojure's own REPL, so it wouldn't have to reimplement its functionality.
Probably that'd be fine. What exactly does `:preserve` do? If it doesn't affect the evaluation then we can safely enable it.
I thinking `delay`ing those shouldn't be an issue. I have to admit I rarely think about such micro-optimizations, as I hope most people don't get to start/restart CIDER/Calva/whatever often. :-)