Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
weblocks
+ new post
About this group
Join this group
Hunchentoot 1.2 fixes
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Leslie P. Polzer  
View profile  
 More options Feb 3 2012, 5:24 am
From: "Leslie P. Polzer" <leslie.pol...@gmx.net>
Date: Fri, 3 Feb 2012 02:24:31 -0800 (PST)
Local: Fri, Feb 3 2012 5:24 am
Subject: Hunchentoot 1.2 fixes
Print | Individual message | Show original | Report this message | Find messages by this author
Very little needed changing; Weblocks works with Hunchentoot 1.2.x now.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Scott L. Burson  
View profile  
 More options Feb 18 2012, 4:53 pm
From: "Scott L. Burson" <Sc...@ergy.com>
Date: Sat, 18 Feb 2012 13:53:17 -0800
Local: Sat, Feb 18 2012 4:53 pm
Subject: Re: [weblocks] Hunchentoot 1.2 fixes
Print | Individual message | Show original | Report this message | Find messages by this author
On Fri, Feb 3, 2012 at 2:24 AM, Leslie P. Polzer <leslie.pol...@gmx.net> wrote:

> Very little needed changing; Weblocks works with Hunchentoot 1.2.x now.

I'm not sure what other people are doing about debug mode, since it no
longer seems to be the default to get a backtrace written out to the
browser when an error is caught.  What I'm doing, anyway, is to set
*CATCH-ERRORS-P* to NIL in ENABLE-GLOBAL-DEBUGGING; this causes
Hunchentoot not to set up a handler for ERROR at all -- instead,
errors bring up a SLIME debug window.  I prefer it this way, as I can
interact with the error context.

What do other Weblocks users think?

-- Scott


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google