From: David L. <da...@li...> - 2003-11-02 17:00:34
Attachments:
aclrepl-globals.diff
|
sb-aclrepl sets some global variables which should really be specific to each REPL instance (in different threads). Patch attached. An unrelated question: Does anyone else see an empty line before results are printed? Reversing the order of FRESH-LINE and PRIN1 in REP-ONE seems to help for me (why is there a comment right before the FRESH-LINE which explains that FRESH-LINE should not be called?). It does not help under all circumstances though -- a listener on a socket connection to LEP suddenly works, but on an ordinary terminal it does not. ---------------- CL-USER(12): 'like-that LIKE-THAT CL-USER(13): ---------------- David -- Schrei es ihnen ins Gesicht! Soylent Gruen ist Menschenfleisch! |
From: <xa...@xa...> - 2003-11-02 18:38:41
|
On Sun, Nov 02, 2003 at 06:00:25PM +0100, David Lichteblau wrote: > sb-aclrepl sets some global variables which should really be specific to > each REPL instance (in different threads). Patch attached. Cool. I wrote a cheesy little thing that pops up a new listener in an xterm, but it confused sb-aclrepl and I wasn't sure how to fix it. The files are here: http://www.xach.com/tmp/xterm-listener/ wserv.c is from the ircII sources and has been slightly modified. Zach |
From: Kevin R. <ke...@ro...> - 2003-11-03 18:55:45
|
David Lichteblau wrote: > sb-aclrepl sets some global variables which should really be specific to > each REPL instance (in different threads). Patch attached. Thanks for the patch, I'll apply it. > An unrelated question: Does anyone else see an empty line before results > are printed? Reversing the order of FRESH-LINE and PRIN1 in REP-ONE > seems to help for me (why is there a comment right before the FRESH-LINE > which explains that FRESH-LINE should not be called?). It does not help > under all circumstances though -- a listener on a socket connection to > LEP suddenly works, but on an ordinary terminal it does not. Sure, it's there. I've look at ways to avoid this while robustly ensuring the output of the evaluated form starts on its own line. The origin of the issue is that newline entered on the input stream does not reset the output column on the output stream. So, the fresh-line on the output-stream generates another newline. I've tested various work-arounds, but have not found a robust solution. Unless a robust solution is found to ensure the output starts on its own line, I think having the empty line is best solution. I agree, the comment before fresh-line is confusing. I'll update the comment about the issue. Kevin |