On Friday, February 12, 2016 at 9:51:50 AM UTC+1, Scaramaccai wrote: > > > > On Thursday, February 11, 2016 at 9:54:19 PM UTC+1, Sean Corfield wrote: >> >> Scaramaccai wrote on Thursday, February 11, 2016 at 8:32 AM: >> >I'm learning Clojure, and I find difficult to understand where a >> specific compiler error happens: >> >> The stacktraces can be pretty daunting at first, unfortunately. >> >> How are you compiling / running the code? That will have some bearing on >> how errors are reported. >> >> > Yes, the problem seems to be how I compiled the code. I was using > Vim+Fireplace, and doing a "cpr" (takes the content from the active buffer > and requires it inside the REPL) I had the error without a proper > stacktrace (see below). Running using "reipl run" gives the "proper" > stacktrace: >
BTW using (.printStackTrace *e) >From inside the REPL gave me the full stack... so I can actually keep using Fireplace and get the full stack when needed. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
