Thanks, Alex. I didn't know about *e or Throwable->map.
-austin
On Wednesday, October 24, 2018 at 9:07:44 PM UTC-7, Alex Miller wrote:
>
> Re clj / the built-in repl:
>
> user=> (doc pst)
> -
> clojure.repl/pst
> ([] [e-or-depth] [e depth])
> Prints a stack trace of the
Re clj / the built-in repl:
user=> (doc pst)
-
clojure.repl/pst
([] [e-or-depth] [e depth])
Prints a stack trace of the exception, to the depth requested. If none
supplied, *uses the root cause* of the
most recent repl exception (*e), and a depth of 12.
That is, it on
Thanks. I would not have thought to check that.
These are the processes running after launching each REPL.
$ clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta4"}}}'
Does not include cause.
rlwrap -r -q \" -b (){}[],^%3@";:' clojure -Sdeps {:deps
{org.clojure/clojure {:mvn/vers
I am not sure if this is the reason, but I would recommend checking the
command line options used when starting the java process in these cases.
Leiningen uses some command line options by default, for faster startup
times I think, that might affect how much detail is captured in stack
traces when
I don't understand what is going on here. I'm trying to throw an exception
with a cause and sometimes the cause is included in the stacktrace and
sometimes it isn't.
~$ clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta4"}}}'
Clojure 1.10.0-beta4
user=> (try (/ 1 0) (catch Except
