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

Broken Tests and Submitting a Patch
by Samuel Freilich 08 Apr '15

08 Apr '15

I use SLIME for work (at Google, on ITA Software's QPX) and would like to submit improvements. In particular, we'd like to be able to use slime-cl-indent for Common Lisp indentation without any custom patches related to loop indentation, but we need a few more customization options. So two things: 1. Revision 1.68 of slime-cl-indent ( http://common-lisp.net/viewvc/slime/slime/contrib/slime-cl-indent.el?r1=1.6…) breaks many tests. I think that should be reverted (or at least replaced with something that has the expected behavior). 2. I'd like to submit the attached patch. It introduces a few customization options we want, makes the common-lisp-body-introducing-loop-macro-keyword and common-lisp-indent-indented-loop-macro-keyword regexps more comprehensive, and includes tests for the new customization options (all new tests pass without reverting 1.68, though a bunch of old tests still fail unless 1.68 is reverted). Peace, -Sam

2 2

GitHub workflow for the SLIME repo
by Luís Oliveira 08 Apr '15

08 Apr '15

One thing we should agree on is how to merge pull requests. This blog post presents the three alternatives: <http://differential.io/blog/best-way-to-merge-a-github-pull-request>. The first option is clearly the easiest since all you have to do is click GitHub's merge button, but I personally find that the merge commits pollute the history (particularly if only one or two commits are being merged). I know João disagrees with me on this matter. It's pretty easy to implement the other workflows with a couple of commands, something like: # see <https://help.github.com/articles/checking-out-pull-requests-locally> # on an up-to-date repo $ git checkout pr/66 $ git rebase origin/master $ git push origin pr/66:master Or using hub (<http://hub.github.com>): # on an up-to-date master $ hub am https://github.com/slime/slime/pull/66 $ git push I'm partial to the second option listed on the blog post, but I have very few commits in SLIME so my opinion should weight very little. :-) Cheers, -- Luís Oliveira http://kerno.org/~luis/

4 4

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