[slime-cvs] CVS update: slime/PROBLEMS

[Helmut Eller]

Update of /project/slime/cvsroot/slime
In directory common-lisp.net:/tmp/cvs-serv22955

Modified Files:
	PROBLEMS 
Log Message:
Mention READ-CHAR-NO-HANG brokeness.

Date: Mon Nov 21 00:31:56 2005
Author: heller

Index: slime/PROBLEMS
diff -u slime/PROBLEMS:1.7 slime/PROBLEMS:1.8
--- slime/PROBLEMS:1.7	Tue Jun 28 10:40:07 2005
+++ slime/PROBLEMS	Mon Nov 21 00:31:56 2005
@@ -11,6 +11,13 @@
 The listen socket is bound on the loopback interface in all Lisps that
 support this. This way remote hosts are unable to connect.
 
+** READ-CHAR-NO-HANG is broken
+
+READ-CHAR-NO-HANG doesn't work properly for slime-input-streams.  Due
+to the way we request input from Emacs it's not possible to repeatedly
+poll for input.  To get any input you have to call READ-CHAR (or a
+function which calls READ-CHAR).
+
 * Backend-specific problems
 
 ** CMUCL
@@ -23,7 +30,8 @@
 
 The latest released version of SBCL at the time of packaging should
 work.  Older or newer SBCLs may or may not work.  Do not use
-multithreading with unpatched 2.4 Linux kernels.
+multithreading with unpatched 2.4 Linux kernels.  There are also
+problems with kernel versions 2.6.5 - 2.6.10.
 
 The (v)iew-source command in the debugger can only locate exact source
 forms for code compiled at (debug 2) or higher. The default level is
@@ -57,15 +65,18 @@
 you may have to start CLISP with "clisp -K full".
 
 Under Windows, interrupting (with C-c C-b) doesn't work.  Emacs sends
-a signal 2 (= SIGINT), but the signal is either ignored or CLISP exits
+a SIGINT signal, but the signal is either ignored or CLISP exits
 immediately.
 
-The backtrace doesn't include frames for compiled functions.  Changes
-to CLISP's C code are needed to fix this problem.
-Interpreted code is usually easer to debug.
+Function arguments and local variables aren't displayed properly in
+the backtrace.  Changes to CLISP's C code are needed to fix this
+problem.  Interpreted code is usually easer to debug.
 
 M-. (find-definition) only works if the fasl file is in the same
 directory as the source file.
+
+The arglist doesn't include the proper names only "fake symbols" like
+`arg1'.
 
 ** Armed Bear Common Lisp