I know of no way that older exceptions than *e are automatically saved
anywhere (unlike the results of previous REPL expressions, of which the
last 3 are saved in *1 *2 *3).

When an exception occurs, it is probably much less error-prone to type a
short expression like (def e1 *e) to save the exception in e1, even if
another exception occurs after that which modifies *e.

Andy


On Thu, Jul 24, 2014 at 6:46 AM, mascip <mas...@gmail.com> wrote:

> Thank you Stuart, this is a very useful answer.
>
> Is there any way to access an exception older than *e?
> What happens to me regularly is to mistype (.printStackTrace *e), which
> makes me lost my previous exception.
>
> -- Pierre Masci
>
>
> On 24 July 2014 13:33, Stuart Sierra <the.stuart.sie...@gmail.com> wrote:
>
>> They're just different versions of the same thing, written at different
>> times by different people, that both got merged into Clojure at different
>> times.
>>
>> Speaking as the original author of clojure.stacktrace, I now think
>> neither one of them should exist. The .printStackTrace method on an
>> exception gives you all the same information and is more reliable.
>>
>> -S
>>
>>
>>
>> On Monday, July 21, 2014 7:30:17 AM UTC-4, Pierre Masci wrote:
>>>
>>> Hi, I'm learning about tools to help me debug from the REPL, and I found
>>> these two with the same name:
>>>
>>>     clojure.stacktrace/root-cause
>>>
>>>     clojure.repl/root-cause
>>>
>>  --
>> 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 a topic in the
>> Google Groups "Clojure" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/clojure/Ic-49W9ZEac/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> clojure+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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.
>

-- 
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.

Reply via email to