On Feb 24, 11:53 pm, Ian Eslick <[email protected]> wrote:
> I noticed that some of the common functionality (http response  
> backtraces, *catch-errors-p* etc no longer work).  We probably need to  
> do our own call to *debugger-hook* in debug mode rather than relying  
> on hunchentoot to do that for us.

Edi Weitz said that he would add back support for this soon.

Not sure how reliable this is though, and considering the usefulness
of this (and tickets [9] and [27]) we should indeed contemplate
adding it ourselves.

[9] http://weblocks.lighthouseapp.com/projects/18897/tickets/9-pretty-backtraces
[27] 
http://weblocks.lighthouseapp.com/projects/18897/tickets/27-optionally-send-email-on-backtrace


> I added a simple version of this to the dispatcher, and also have some  
> minor patches for clozure-cl and updates that broke the elephant  
> backend.  Let me know if there is a better way to send this, it seems  
> a bit of overkill to make a clone just for a small patch... :)

Put the file up somewhere, or paste it to paste.lisp.org
-- Google groups can mess up patches quite well.


> Who is maintaining thecl-jsonversion we're using with weblocks?  I  
> have fixes for that also.

We're using the latest from the official Git repo. Henrik Hjelte is
responsible for that IIRC.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to