[slime-devel] keep getting these messages with latest CVS of SBCL and Slime
In *Messages*-buffer: cond: Wrong type argument: integerp, 0.01 error in process filter: if: tag = slime-result-14-62004 eval-tags = nil sexp = (swank:completions "for" (quote "COMMON-LISP-USER")) error in process filter: tag = slime-result-14-62004 eval-tags = nil sexp = (swank:completions "for" (quote "COMMON-LISP-USER")) This seems to happen whenever Slime wants to show something in the status-buffer (minibuffer?), like argument-lists. I tried downgrading to Slime tagged as FAIRLY-STABLE, but this didn't help. I'm using the package `emacs-snapshot-gtk' (Emacs 22.0.50.1) under Ubuntu Dapper. Anyone else having troubles or know how to solve this?
Lars Rune Nøstdal <larsnostdal <at> gmail.com> writes:
This seems to happen whenever Slime wants to show something in the status-buffer (minibuffer?), like argument-lists.
Correction; it pops up when I press tab to tab-complete something. It also pops up after compiling something - I guess when Slime wants to tell me how many warnings and errors there are. -- mvh, Lars Rune Nøstdal http://lars.nostdal.org/
* Lars Rune Nøstdal [2006-08-14 11:42+0200] writes:
In *Messages*-buffer:
cond: Wrong type argument: integerp, 0.01
This sound's like a problem with accept-process-output. I don't know exactly since when, but CVS Emacs uses milliseconds what used to be microseconds. It also accepts floating point args where older versions required integers. I added a function slime-accept-process-output to hide the differences, but apparently it doesn't work four your version. Does somebody know how to detect which version wants which arguments? Helmut.
Helmut Eller <heller <at> common-lisp.net> writes:
* Lars Rune Nøstdal [2006-08-14 11:42+0200] writes:
In *Messages*-buffer:
cond: Wrong type argument: integerp, 0.01
This sound's like a problem with accept-process-output. I don't know exactly since when, but CVS Emacs uses milliseconds what used to be microseconds. It also accepts floating point args where older versions required integers.
I added a function slime-accept-process-output to hide the differences, but apparently it doesn't work four your version.
Got latest from CVS now; brute-force works here. TY :) -- mvh, Lars Rune Nøstdal http://lars.nostdal.org/
participants (2)
-
Helmut Eller -
Lars Rune Nøstdal