slime-devel

slime-devel@common-lisp.net

4231 discussions

ChangeLog file
by joaotavora＠gmail.com 08 Apr '15

08 Apr '15

Luís Oliveira <notifications(a)github.com> writes: > FWIW, I find the ChangeLog distracts people from more IMHO more important > efforts such as updating the NEWS file or writing a proper commit message > describing why something has changed rather than what. I don't agree at all: you *should* describe in the ChangeLog or commit messages **why you changed what**. In the NEWS file, you describe the user-visible aspects of your change. The ChangeLog format can hardly be blamed for any lazyness to write proper commit messages, indeed it encourages the opposite. The information in SLIME's ChangeLog has been invaluable to my recent hackings, for example. I refer you to the discussion in emacs-devel, they're getting rid of the ChangeLog file, but not its format. Still, Helmut, I propose that we get rid of the ChangeLog files and use commit messages exclusively. I've noticed that with no such file, pressing C-x 4 a will still create a (dummy) ChangeLog file with the prettily formatted entries. You just don't commit it and it can probably be ignored in .gitignore. Then, a fairly recent Emacs's built-in vc-dir.el will, upon commiting, automatically transpose the text below the date-and-author line is to the commit message buffer. This is extremely convenient and I invite you to try it (in other versions, you have to copy&paste and remove the left indentation manually). Finally, emacs's own "M-x vc-print-log" will give you all the information. The actual diff is only the "=" keybinding away. If Helmut agrees, I see the following steps to enable this in SLIME: * We must find a way to re-implement version checking between SLIME and Swank that is portable across all installation options. slime.el can parse itself on compile/load to look for the ";; Version:" cookie (that MELPA and other automated builders also look for, incidently). swank.lisp would have to do something similar in portable Common Lisp to report its own version in a variable. * Listing the contributors in the manual depends on the ChangeLog, but that can be delegated to some variation of git log | grep Author: | cut -d ' ' -f 1 --complement | sort | uniq except for the authors of patches that were commited by someone else in the CVS days. * The CONTRIBUTING.md file has to be updated. Anyone up to perform these changes? João

3 4

tests for contrib/slime-cl-indent.el are broken
by Robert Brown 08 Apr '15

08 Apr '15

You can verify tests are broken if you M-x load-file slime-cl-indent.el then evaluate the following in *scratch* (progn (setq lisp-indent-function 'common-lisp-indent-function) (common-lisp-run-indentation-tests t)) The root cause is complicated. Setting comment-column to nil in the buffer used for testing fixes things. Bob Index: slime-cl-indent-test.txt =================================================================== RCS file: /project/slime/cvsroot/slime/contrib/slime-cl-indent-test.txt,v retrieving revision 1.22 diff -u -r1.22 slime-cl-indent-test.txt --- slime-cl-indent-test.txt 13 Apr 2012 16:16:11 -0000 1.22 +++ slime-cl-indent-test.txt 22 Nov 2013 23:26:18 -0000 @@ -348,9 +348,6 @@ (bar)) ;;; Test: 32 -;; -;; comment-indent-function: (lambda () nil) -;; comment-column: nil (unknown (;; KLUDGE: comment-indent hackery to get ;; the comment right. Otherwise we get a Index: slime-cl-indent.el =================================================================== RCS file: /project/slime/cvsroot/slime/contrib/slime-cl-indent.el,v retrieving revision 1.68 diff -u -r1.68 slime-cl-indent.el --- slime-cl-indent.el 3 Jan 2013 12:40:52 -0000 1.68 +++ slime-cl-indent.el 22 Nov 2013 23:26:18 -0000 @@ -33,6 +33,8 @@ ;;; Code: +(require 'cl) + (defgroup lisp-indent nil "Indentation in Lisp." :group 'lisp) @@ -1755,6 +1757,11 @@ (defun common-lisp-indent-test (name bindings test) (with-temp-buffer (lisp-mode) + ;; We've installed a comment-indent-function that returns nil, so that + ;; comment-indent always calls indent-according-to-mode. Unfortunately, it + ;; shifts comments to comment-column, if there's text before the comment. + ;; Turn that behavior off by setting comment-column to nil. + (setq comment-column nil) (setq indent-tabs-mode nil) (common-lisp-set-style "common-lisp-indent-test") (dolist (bind bindings)

2 2

Re: [slime] swank-loader could use ASDF (#65)
by joaotavora＠gmail.com 08 Apr '15

08 Apr '15

[CCing slime-devel] François-René Rideau <notifications(a)github.com> writes: > On SBCL, (time (require :asdf)) takes .15s, but total SLIME startup > time is about 3s, so ASDF doesn't seem to be the bottleneck. I didn't say that it was, and yes that matches my times. I am mostly curious as to the proportion of ABCL's 2 seconds to the total current SLIME startup time. > On most implementations, you don't need to compile asdf if you use the > implementation's provided ASDF (assuming it's recent > enough). > > Otherwise, yes, the first time around, you get to compile asdf — but > hopefully, that's only the case on SCL. It's also the case on most Allegros. Even 9.0 doesn't have the newest ASDF, it seems to have 2.23.7. But a one-time wait per lisp implementation is not so bad for me. > Yes, it makes sense to me that each slime extension should get its own > directory, its own .asd file, etc. In case it wasn't clear, the mock tree I gave in the last email were the contents of the ~/.emacs.d/elpa dir after installation. So the slime source repo, the main .asd file can be still be the "all in one" that you propose in pull request #80. Those small .asd files can easily be auto-generated when packaging. Maybe this makes sense so as not to disrupt the current repo organization too much. In the el-get case, the installed software in ~/.emacs.d/el-get *is* the source repo. So non-third-party contribs are loaded slightly differently, while third-party contribs would be just like in the ELPA case. > There's a slight issue of how to communicate the search path between > Emacs and ASDF, however: push things to the central-registry? Is let-binding ASDF:*CENTRAL-REGISTRY* very bad? I sometimes do that and it works ok. We could set it to the same path where we have the .el file. This would have to be tested and as robust as possible of course. > source-registry? Add an Emacs-specific sysdef search function? I'm not familiar with any SOURCE-REGISTRY var. And also would avoid, if possible, replicating in emacs-lisp what might already be in ASDF. João

1 0

Re: slime on github
by Paul Bowyer 08 Apr '15

08 Apr '15

Hello João, If you recall, I mentioned some error messages that occurred in the slime *messages* buffer when I tried to load log4cl: error in process filter: ad-Orig-slime-repl-emit: Text is read-only error in process filter: Text is read-only Well, this afternoon I was trying to track down a problem related to some work I was doing and I went to the *inferior-lisp* buffer and entered (sb-ext:describe-compiler-policy). That produced the following error message in the *messages* buffer: error in process filter: slime-repl-emit: Text is read-only error in process filter: Text is read-only If I enter (sb-ext:describe-compiler-policy) in the repl, I get normal output in the repl. Do I have some configuration issues, or is there some reason I can no longer use the *inferior-lisp* buffer for direct entry of lisp commands? I'm using emacs 23.4.1 and sbcl-1.13 if that's important. Paul Bowyer

2 8

Typos on SLIME tutorial
by Borja Tarraso 08 Apr '15

08 Apr '15

Hi, I was reading the SLIME tutorial and I found two typos. They are in the pdf (at least - did not check the other flavours like HTML that are online): Page 18 (13 from PDF file): just when it is explaining slime-compiler-macroexpand : where it says "Repeatedy expamd" -> should be "Repeatedly expand". Page 19 (14 from PDF file) just when it is explaining slime-inspector-operate-on-point : where it says "inspcetor" -> should be "inspector". Best regards, Borja Tarraso

2 1

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

08 Apr '15

Hello everyone, It's time for another freeze. Please focus on testing and fixing regressions since the last release. I plan to do the release dance either Sunday or Monday. Cheers, -- Luís Oliveira http://kerno.org/~luis/

1 0

slime-repl buffer
by Fabrice Popineau 08 Apr '15

08 Apr '15

Hi, Is there anyway to limit the size of the repl buffer ? Something like 10000 lines max for example. Emacs slows a lot with large buffers. Best regards, -- Fabrice Popineau ----------------------------- SUPELEC Département Informatique 3, rue Joliot Curie 91192 Gif/Yvette Cedex Tel direct : +33 (0) 169851950 Standard : +33 (0) 169851212 ------------------------------

4 7

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel