Fork me on GitHub
#cursive
<
2018-12-13
>
caleb.macdonaldblack00:12:16

Any way to get vector destructuring to align in let bocks?

cfleming01:12:42

@caleb.macdonaldblack No, there isn’t unfortunately. Those blocks can often be very long, and there’s no way to say to the IntelliJ formatter “align as long as the key is not longer than 20 chars”.

cfleming03:12:49

@alexmiller Cursive now (or will soon) just print a single line from the exceptions leading up to the root cause, and then the full trace from the root cause.

👍 24
cfleming06:12:25

@alexmiller Looking at the new 1.10 error handling stuff, it looks like if I reuse the (-> ex Throwable->map clojure.main/ex-triage clojure.main/ex-str) then the actual stacktrace is never printed. Is that just designed for showing an error at the REPL, and then the user prints the stacktrace if required? i.e. should the print stacktrace action still do more or less like the above even on 1.10?

alexmiller13:12:16

It’s always been the case that the main repl doesn’t print the stack trace.

alexmiller13:12:49

So, this is the “normal” case from my perspective

cfleming23:12:00

Ok, thanks, just making sure I wasn’t missing something new.

cfleming07:12:26

After some testing, I’m going to go for yes, since the new errors are automatically already printed, presumably by the new exception printing machinery, on 1.10.

torbjornvatn11:12:10

Has anyone got any tips on how to get Cursive to resolve Javascript dependencies from NPM? I use shadow-cljs and deps.edn as described in this blog post https://andrearichiardi.com/blog/posts/clojurescript-cursive-shadow-setup.html

cfleming23:12:25

@torbjornvatn Sadly no, but it’s something I’m planning to fix.