vemv

> Perhaps we should also document the JavaFX workaround in the README (e.g. under "Caveats")? Yes. Although it's also true that cider-nrepl breaks altogether, which we should prevent from happening...

Hi, sorry, I'd really appreciate the discussion not going off rails. I've already spent a lot of time leaving this in a usable and performant manner for a wide variety...

Yes, without Enrich, Orchard won't have access to javadocs that can be parsed (btw, Enrich had some bumpy beginnings but I'd encourage you to try it out - I hear...

@alexander-yakushev a possibly easy subset of this problem is making sure that stacktraces have a reasonable length limit by default. At the moment (cider-nrepl latest stable) they can create a...

Thanks! I'd go for the latter - seems a generalized fix for an area that could slow down Emacs (so it's reasonable to consider this broken already) --- Not sure...

Thanks for the response. Indeed the `matcher-combinators` project surely has a green build and therefore the issue cannot be always reproduced. However, did you check out the names of the...

Hi again! Did you check out the name of the var that gets created by evaluating `(tabular (fact ...` in a repl? As mentioned, this var name seems fishy in...

Alright, I'll try to provide a repro repo, as this might be related to an unlucky combination of deps or such

> But when I evaluate them from Cider/Emacs (C-c C-k) I'm getting compiler exception. We both use CIDER so yeah that's a lead :) Could you post the root exception?...

@philomates As a humble suggestion, I wonder if it has to do with some `^:dynamic` var; for example most (if not all) Clojure test runners assume that `*ns*` equals `(the-ns...