#Q 1.2-1) How should I report bugs?
#Q 1.2-2) dribble-bug output seems to lag behind Lisp I/O.
#Q 1.2-3) Sometimes CL output is not logged in the dribble-bug file. What
do I do about this?
#Q 1.2-4) Is there a mailing list for Allegro CL? How do I sign up?
Q 1.2-1) How should I report bugs?
A 1.2.1) Use dribble-bug, documented in the document <Allegro directory>/doc/cl/introduction.htm and <Allegro directory>/doc/cl/pages/operators/excl/dribble-bug.htm.
Q 1.2-2) dribble-bug output seems to lag behind Lisp I/O.
A 1.2-2) dribble-bug always catches up with the Lisp I/O (which is stored in a buffer before it goes into the dribble file). If you would like to see output in the dribble file faster, you can try using the following hack before calling dribble:
(excl:advise dribble :around nil nil (let ((excl::stream-buffer-size 1)) :do-it))
Q 1.2-3) Sometimes CL output is not logged in the dribble-bug file. What do I do about this?
A 1.2-3) This should only occur when using the foreign-function interface or running a shell function with run-shell-command and friends. Some messages from foreign code may be written directly to Unix stdout or stderr, bypassing Lisp entirely. To circumvent this problem, you can either use an Emacs buffer or the Unix utility "script" to save the entire transaction record.
Q 1.2-4) Is there a mailing list for Allegro CL? How do I sign up?
A 1.2-4) Yes, there is a mailing list for Allegro CL users. It is accessed through the address allegro-cl@cs.berkeley.edu. To be added to or deleted from this list, send mail to allegro-cl-request@cs.berkeley.edu. Franz periodically makes announcements on this mailing list, but its main purpose is to allow users of Allegro CL (both Unix and Windows) to communicate with each other, sharing ideas, complaints and code.
© Copyright 1998, Franz Inc., Berkeley, CA. All rights reserved.
$Revision: 1.1.2.10 $