16 Dec
2006
16 Dec
'06
10:42 p.m.
On Sat, 16 Dec 2006 17:27:33 -0500, vedm mlist@rogers.com wrote:
Edi Weitz edi@agharta.de writes:
On Sat, 16 Dec 2006 14:18:03 -0500, vedm mlist@rogers.com wrote:
If I set *CATCH-ERRORS-P* to T I do not see this error.
Strange, and how did you get the backtrace then?
That backtrace appears only when *CATCH-ERRORS-P* is set to nil (not to T).
Sorry, I was confused... :)
Basically, mx explanation in the other email was right except for the logging part. There should /probably/ be some cleanup that prevents errors like this one (that aren't really errors) to pop up the debugger.