Forum OpenACS Q&A: Response to What happened to servername-error.log

Posted by Jerry Asher on
I never got TclPro and AOLserver to work 100% of the time.  It seemed that every other breakpoint was caught, but I suspect that was due to operator error.
Yes there has got to be a better way to debug code.  When developing pages, I feel that I've fallen back 20 years to
I have a bit more sophisticated version of that.  The combination of <tt>nscp</tt>, emacs, and David Lutterkort's emacs server log module, <a href='';></a>, are a win for me.
I typically have one emacs window on the code, an emacs window shelled into AOLserver itself through <tt>nscp</tt>, an emacs window serving the log, and an emacs window in <tt>SQL</tt> mode.
Truly the big win is <tt>nscp</tt> mode which lets me evaluate arbitrary AOLserver tcl expressions and communicate with the running AOLserver itself.  It's a Lisp Interaction buffer supported by AOLserver.
I also find that having browsers open to the Tcl manual at activestate, the aolserver manual at aolserver, and a Guide to Semiconductor Physics at is also helpful.