- slime-devel - mailman3.common-lisp.net

Attempt to unread too many characters ...
by Andrew Myers 08 Apr '15

08 Apr '15

My office mate and I both use Slime with Franz Allegro Lisp and we both see this problem. It's been occuring for the past couple of years since we started using slime and I'm finally annoyed enough with it to dig in and try to fix it. If anyone can point me in the right direction it would be appreciated. The problem: In short, any restart which tries to take an argument causes the error > attempt to unread too many characters on > #<TWO-WAY-STREAM "" @ #x10000ee1ad2> > [Condition of type SIMPLE-ERROR] For example, in a fresh REPL: > ; SLIME 2013-09-29 > CL-USER> a Which results in: > Attempt to take the value of the unbound variable `A'. > [Condition of type UNBOUND-VARIABLE] > > Restarts: > 0: [TRY-AGAIN] Try evaluating A again. > 1: [EVALUATE-ALTERNATIVE] Use :A instead. > 2: [STORE-VALUE] Set the symbol-value of A and use its value. > 3: [USE-VALUE] Use a value without setting A. > 4: [RETRY] Retry SLIME REPL evaluation request. > 5: [*ABORT] Return to SLIME's top level. > --more-- Select restart #2 and enter the value 10 > enter an expression which will evaluate to a new value: 10 Results in: > attempt to unread too many characters on > #<TWO-WAY-STREAM "" @ #x100010c8c22> > [Condition of type SIMPLE-ERROR] > > Restarts: > 0: [EVALUATE-ALTERNATIVE] Use :A instead. > 1: [STORE-VALUE] Set the symbol-value of A and use its value. > 2: [USE-VALUE] Use a value without setting A. > 3: [RETRY] Retry SLIME REPL evaluation request. > 4: [*ABORT] Return to SLIME's top level. > 5: [ABORT] Abort entirely from this (lisp) process. Is this a problem with Franz Lisp? Slime, Swank? I'm not really sure where I should start looking at this point. Any help is appreciated. Thanks, Andrew Myers

3 5

Moving to GitHub and cl-lib
by Helmut Eller 08 Apr '15

08 Apr '15

As you may have heard, we're moving the SLIME repository to GitHub. The new location is: https://github.com/slime/slime The bug tracker will also be moved from Lunchpad to GitHub. João Távora has already done some work in the new repository. In particular SLIME now requires the cl-lib library. As you probably know, the Emacs maintaners have declared the cl library obsolete, and encourage everybody to use the new names. What used to be "find" from the cl library is now called "cl-find" and in the cl-lib library. If you're using Emacs 23 then you need to install cl-lib manually, i.e. grab the .el file from http://elpa.gnu.org/packages/cl-lib.html and drop it somewhere into Emacs' load-path. Is that too much hassle? Should we include scripts to automate this or perhaps include cl-lib-3.0.el in our repo? cl-lib may or may not work with XEmacs. This poses the questions: are there many XEmacs users left? Would you be very unhappy if we drop XEmacs support? Or are you a "I'd be happier with XEmacs but GNU Emacs is also OK" kind of person? Helmut

6 17

Two test errors in latest slime from github
by Paul Bowyer 08 Apr '15

08 Apr '15

Hello everyone, This morning I downloaded the latest slime from github. I have put together a simple bash script to automate the process and as part of that script I run the test suit using: make clean check make check-fancy The results of the test were: Ran 112 tests, 110 results as expected, 2 unexpected (2014-02-21 07:20:38-0800) 1 expected failures 2 unexpected results: FAILED autodoc-tests-23 FAILED autodoc-tests-24 I ran the test suite from the command prompt to check if it was my script causing the problem, but I got the same two errors. This is different from the previous download where I ran the test suite from the command prompt using the same two commands and got no unexpected errors. Respectfully, Paul Bowyer

4 6

Slime REPL becomes non-responsive
by Chintan Pathak 08 Apr '15

08 Apr '15

I am not sure if non-responsive is the ideal description, but when in my program or a REPL command, if I get an error, and I ABORT the execution using 5 as instructed, I get my REPL back. But when I try to execute any command, anything, as simple as(+ 2 3) by pressing return, the line becomes bold, as usual, then there is no output, the execution just hangs there. I have tried, quitting and restarting REPL, that doesnt help. If I restart emacs, then I can start using REPL again normally. Is there a way, I can avoid having to restart emacs every time I make a wrongful REPL execution ?

2 1

Error in *Fuzzy Completions* message
by Sian Mountbatten 08 Apr '15

08 Apr '15

In the *Fuzzy Completions* buffer, the message at the top of the buffer reads: For help on how the use ... It should read: For help on how to use ... In the list of completions, the Flags column shows 8 hyphens, but only 7 flags are listed. What is the meaning of the score? In the target buffer, I was unable to get out of Fuzzy Completion mode. I had to kill the SLIME session and restart. Keying a character which could not be a completion did *not* end the minor mode. -- Dr Sian Mountbatten http://www.poenikatu.co.uk/ Associate member of the FSF no. 10888 Asocia membro de la Libera Programara Fonduso n-ro 10888

2 1

how to setup emacs to auto-load slime and other stuff
by Chintan Pathak 08 Apr '15

08 Apr '15

Hi, I am new to the LISP world and plan to develop on linux using CCL on emacs. I have installed SLIME through quicklisp-slime-helper and made changes to the .emacs.d/init.el file so, that when I do M-x slime in emacs, it brings the CL-USER REPL in emacs. I want to know how I can associate this keychord, so that if I execute emacs from command line in a certain way, then it directly goes to the CL-USER prompt.

3 2

Help redacting the NEWS file
by Luís Oliveira 08 Apr '15

08 Apr '15

Hello SLIME developers, In preparation for the imminent SLIME 2.4 release, I've redacted a NEWS entry with what's changed since the move to GitHub. It'd be too much work to go through the ChangeLog down to October 2011, date of the previous release, so I'm hoping I can use your collective memories instead. Is there something particularly worth mentioning that happened between October 2011 and the move to GitHub? Cheers, -- Luís Oliveira http://kerno.org/~luis/

1 0

Freeze for SLIME 2.4
by Luís Oliveira 08 Apr '15

08 Apr '15

Hello everyone, As discussed a few weeks ago, I intend to release SLIME 2.4 next weekend. In the meantime, in a similar vein to the SBCL release process, I'd like to propose a freeze period where we focus on testing and fixing regressions since the move to GitHub. (Helmut, does this process sound good to you?) So, I invite users to go to https://github.com/slime/slime to grab the latest SLIME via either Git or the ZIP download link, and report any issues using GitHub's issue tracker. Pull requests are likewise most welcome. :-) Cheers, -- Luís Oliveira http://kerno.org/~luis/

4 6

[patch] RET on no part in *inspector* buffer
by João Távora 08 Apr '15

08 Apr '15

I wonder if anyone else is seeing the same error in the latest slime. Press RET any non-interactive part of the *slime-inspector* buffer and get a "wrong number of arguments" error instead of the intended "no object at point". Here's a possible patch: diff --git a/slime.el b/slime.el index 106b0fa..38df505 100644 --- a/slime.el +++ b/slime.el @@ -6645,16 +6645,16 @@ that value. 2. If point is on an action then call that action. 3. If point is on a range-button fetch and insert the range." (interactive) - (let ((opener (lexical-let ((point (slime-inspector-position))) + (let* ((opener (lexical-let ((point (slime-inspector-position))) (lambda (parts) (when parts (slime-open-inspector parts point))))) (new-opener (lambda (parts) (when parts - (slime-open-inspector parts))))) - (destructuring-bind (property value) - (slime-inspector-property-at-point) - (case property + (slime-open-inspector parts)))) + (property-at-point (slime-inspector-property-at-point)) + (value (second property-at-point))) + (case (first property-at-point) (slime-part-number (slime-eval-async `(swank:inspect-nth-part ,value) new-opener) @@ -6664,7 +6664,7 @@ that value. (slime-action-number (slime-eval-async `(swank::inspector-call-nth-action ,value) opener)) - (t (error "No object at point")))))) + (t (error "No object at point"))))) (defun slime-inspector-operate-on-click (event) "Move to events' position and operate the part." -- João Távora

1 1

error in process filter: Keyword argument :coding-system not one of (:coding-systems)
by Thorsten Jolitz 08 Apr '15

08 Apr '15

Hi List, I continue to get this error ,-------------------------------------------------------------------- | error in process filter: Keyword argument :coding-system not one of | (:coding-systems) `-------------------------------------------------------------------- when calling Slime with a PicoLisp swank implementation, besides having changed the :encoding to what I believe is a valid value. original version: ,-------------------------------------------------------------------- | (de swank:connection-info () | (list | ':pid *Pid | ':style 'nil | ':encoding '(:coding-system "utf-8" :external-format "utf-8") [...] `-------------------------------------------------------------------- changed to new version: ,------------------------------------------------ | (de swank:connection-info () | (list | ':pid *Pid | ':style 'nil | ':encoding '(:coding-system "utf-8-unix") [...] `------------------------------------------------ What am I missing here? PS I just recently cloned the newest slime from the 'unofficial' github repo. -- cheers, Thorsten

1 0