Cursive doesn't always correctly link line numbers in exceptions. For example, I'm in a project that contains compute.db.formulas namespace. The below exception highlights everything except the calls from that namespace.

On that ^, I think it'd be useful to highlight stacktrace lines that are a part of the current project/module.

@kenny That’s odd, I’ll try to reproduce that, thanks.

After I changed the file extension to clj, it worked. I need cljc though.

Ok, I’ll fix that.

@cfleming Also in the same space, Spec instrumentation exceptions printed from the tests are not formatted at all. This makes reading these traces really difficult. I actually don't think this has to do with the clojure.test integration though because if I copy the test to the REPL and run it, the resulting exception is also not formatted.

example? might be something we should fix in clojure.test and I'm not sure that's logged anywhere

@alexmiller Can you see the screenshot above?

It appears to be the exception-info formatting - it all is printed on one line.

The above one was particularly nasty because the first line says :path [:argm nil] which, at first, makes no sense. Buried in that text wall is an important piece of info that would've made it immediately obvious what the problem was - :reason "no method".

Even further off topic: it seems like multi-specs should print a similar error to s/keys when a key is missing. For example:

(s/explain (s/keys :req-un [::a]) {})
{} - failed: (contains? % :a)
=> nil
(defmulti example-spec :a)
=> #'compute.db.formulas-test/example-spec
(defmethod example-spec :example 
  [_]
  (s/keys :req-un [::example]))
=> #object[clojure.lang.MultiFn 0x645f9f2 "clojure.lang.MultiFn@645f9f2"]
(s/explain (s/multi-spec example-spec :a) {})
{} - failed: no method at: [nil]
=> nil

the key is not being used as a key, but as a function, and falling through to :default case is perfectly fine

there may still be something more that can be done here, but this tool is more generic than you're assuming

If I was really really eager to have an “Extract function” automated refactoring, is there any path forward for me? Can I bribe you @cfleming?

or implement it myself?

How do you guys pass system environment variables to a Local REPL? IntelliJ seems to have some odd pattern of reading in the environment vars. In the Run Config modal under the System Environment modal, I can see the env vars IntelliJ reads. I can update my PATH env var by changing it in my ~/.profile. However, if I add a new env var to my ~/.profile, IntelliJ won't read that in.

Another example of an exception that is not linked.

@kenny Are you on the latest Cursive? I made some fixes there for the new 1.10.1 exceptions which include a path.

I'm on v1.8.2-eap4-2018.3. Had to downgrade to 2018.3. Too many problems with 2019 version: indexing issue, paren highlights, & random CPU spikes.

Yeah, 2019 has been really bad for issues affecting Cursive.

Ok, I’m going to do a pass over all those matching filters, I’ve received a bunch of examples to fix recently.

The Help > Check for updates didn't show any Cursive updates so I think that's the latest version. I'm running Clojure 1.10.1.

Yeah, that’s the latest one.

Is the above exception-info formatting a clojure or cursive issue?

I haven’t had time to look at it, but if it happens in a normal REPL too it’s likely to be Clojure.

Certain exception infos are printed nicely though. A simple example:

Even a simple instrument exception prints nicely.