Hi, this will be very quick.
It seems nobody got bitten by that yet, so I guess I should leave a trace "on the internet": using slime with emacs' print-level set will fail badly. I suspect print-length is equally dangerous.
petdog petdog@gmail.com writes:
Hi, this will be very quick.
It seems nobody got bitten by that yet, so I guess I should leave a trace "on the internet": using slime with emacs' print-level set will fail badly. I suspect print-length is equally dangerous.
long ago i changed print-length and print-level in slime-pprint-event to nil, i've never had a problem. what issue did you run into?
On Thu, 01 May 2008 18:00:38 +0200, Marco Baringer wrote:
long ago i changed print-length and print-level in slime-pprint-event to nil, i've never had a problem. what issue did you run into?
The problem is slime sending garbled sexps to the inferior lisp, and binding print-level and print-length to nil in slime-net-send does indeed solve the problem.
For a simple demonstration, just try to use fuzzy-completion with print- level = 5.
* petdog [2008-05-01 19:28+0200] writes:
The problem is slime sending garbled sexps to the inferior lisp, and binding print-level and print-length to nil in slime-net-send does indeed solve the problem.
For a simple demonstration, just try to use fuzzy-completion with print- level = 5.
This should be fixed in CVS. Thanks for the report.
Helmut.
-
Helmut Eller -
Marco Baringer -
petdog