slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] reconnect slime to lisp
by David Steuber 24 Apr '04

24 Apr '04

If you enter my subject line into Google and are feeling lucky, you will find Bill Clemontson's blog on the subject. I had slightly different needs than what he described though. Here's my deal. Using a script, I want to start up a lisp session that runs as a web application server on a remote host. At arbitrary times, I wish to be able to connect to this lisp session and modify the running process. I connect to the remote host using the 'ssh -X' command and run Emacs from there. That is the Emacs I want to connect to my running lisp. I'm using SBCL on Linux (Debian/testing with my own 2.6.5 kernel). The SBCL is from CVS with sb-thread and sb-futex enabled. I've got KMR's cl-modlisp standing in for my application server at the moment. Its debug page is a good way to test that I've got Apache talking to SBCL. I'm also using detachtty. I find this very convenient. Basicly, my only remaining problem (other than writing web applications) is to create a run control script for /etc/init.d/ so that SBCL can be started, stopped, and restarted in the same fashion as apache. This seems to be working. This makes me very happy. I suppose I should mention that I have an sbclrc file that requires asdf and asdf-install. I am also using the var for the swank communication style rather than assuming :spawn. This works because the symbol was exported. The anounce-fn was not exported. I am using a simple lambda because it really doesn't need to do anything. Here is the script: #!/bin/sh # # Start SBCL as a detachtty process and start listening to Apache # # Swank is used so that SLIME can connect to the running process at # any time. Consider this a huge security hole. # rm /home/david/usr/var/run/lisp-dribble 2>/dev/null rm /home/david/usr/var/run/detachtty.log 2>/dev/null rm /home/david/usr/var/run/lisp.pid 2>/dev/null rm /home/david/usr/var/run/lisp-socket 2>/dev/null export SBCL_HOME=/home/david/usr/lib/sbcl /usr/bin/detachtty --dribble-file /home/david/usr/var/run/lisp-dribble \ --log-file /home/david/usr/var/run/detachtty.log \ --pid-file /home/david/usr/var/run/lisp.pid \ /home/david/usr/var/run/lisp-socket \ /home/david/usr/bin/sbcl \ --eval "(asdf:operate 'asdf:load-op :modlisp)" \ --eval "(asdf:operate 'asdf:load-op :swank)" \ --eval "(ml:modlisp-start :port 3000)" \ --eval "(swank:create-swank-server 4005 swank:*communication-style* #'(lambda (p) p) t)" -- I wouldn't mind the rat race so much if it wasn't for all the damn cats.

1 0

[slime-devel] Hyperdoc directions
by Nikodemus Siivola 24 Apr '04

24 Apr '04

First some background to get everyone up to speed: Hyperdoc is a project to provide CLHS-style documentation lookup for libraries. http://www.common-lisp.net/project/hyperdoc/ Edi Weitz recently added support for the hyperdoc protocol to his packages, and the hyperdoc CVS contains horrid buggy hack in slime.patch which replaces the clhs lookup in Slime by similar functionality powered by hyperdoc. (Hyperdoc delegates undocumented symbols to hyperspec-lookup <http://www.common-lisp.net/project/hyperspec-lookup/>.) Calling (hyperdoc:lookup package-name symbol-name &optional doc-type-name) gives either NIL, an URI, or if multiple docs for the same symbol exist an alist of the form ((doc-type-name . uri)*). The URIs related to a package can be stared in files, and if this has been done with (hyperdoc:generate-index package), then lookup can be done even if the package is not loaded. The idea is that these lookup files could also be used directly by Slime/Emacs if it isn't connected to a lisp. In it's current state it's basically usable, but some refinements are probably necessary for serious use: 1) Hook the index generation to compiling, either by doing (eval-when (:compile-toplevel) (when (find-package :hyperdoc) (funcall (intern "GENERATE-INDEX" :hyperdoc) :this-package))) in client packages, or maybe/preferebly this could be delegated to ASDF. 2) Do the Emacs/Slime binding: * If connected use hyperdoc. * If not connected use the indices and hyperspec.el. * When the query gives multiple results (eg. a structure and a function of the same name) prompt the user to choose which type of documentation should be fetched. "Fair enough, but get to the point already!" Ok, ok... Do people have ideas/opinions on number 1? Once it is done, I think essentially all work on the CL side is complete. Then, if desired, the API can be integrated with cl:documentation or asdf:hyperdocumentation. What do Slime folks think of the Emacs integration? Is someone willing to do the grunt work on it? As the patch to current Slime shows, my elisp-fu and slime-fu are rather lacking. Anything I've forgotten? Cheers, -- Nikodemus

2 1

[slime-devel] Resizing Emacs frame just after starting SLIME
by Paolo Amoroso 24 Apr '04

24 Apr '04

When I start SLIME and resize the Emacs main frame via the window manager's maximize button, the Emacs windows (e.g. those associated with the *scratch* and *slime-repl[1]* buffers) do not adapt to the new size. They remain in the initial configuration. But as soon as I press any key, the windows instantly get the correct size and location. I am using SLIME CVS sources updated a few hours ago, CMUCL 18e and GNU Emacs 20.7.2 under Debian Woody. Paolo -- Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film

3 4

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 24 Apr '04

24 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.345 slime/ChangeLog:1.347 --- slime/ChangeLog:1.345 Thu Apr 22 17:43:34 2004 +++ slime/ChangeLog Fri Apr 23 18:13:08 2004 @@ -1,3 +1,19 @@ +2004-04-24 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-init-connection-state): Use an asynchronous RPC + instead of slime-eval to reduce the amount of work we do in the + timer function. We can remove the workaround for the timer + problem. + +2004-04-23 Luke Gorrie <luke(a)bluetail.com> + + * slime.el: Updated top comments. + Make SLIME faces inherit from their font-lock cousins properly. + (slime-connect): Bind `slime-dispatching-connection' to avoid + being confused by old buffer-local variables when initializing + the connection. This fixes a bug where doing `M-x slime' from the + REPL could give a "Not connected" error. + 2004-04-22 Edi Weitz <edi(a)agharta.de> * slime.el (slime-read-system-name): Perform completion on all

1 0

[slime-devel] list-all-package-names, really all... :)
by Edi Weitz 23 Apr '04

23 Apr '04

Here's another tiny patch. It seems that the function SWANK:LIST-ALL-PACKAGE-NAMES is only used for slime-read-package-name. What about extending it such that nicknames can also be entered? See below. Cheers, Edi.

3 3

[slime-devel] Installation Slime with OpenMCL
by jsdey＠optonline.net 23 Apr '04

23 Apr '04

Greetings: I wanted to fool around with slime to learn lisp. I am caught in a dilemma like which came first the chicken or the egg. Right now the contents of slime.el is unfathonable to me because I am not familiar with the list syntacs. It looks like I am unable to launch swank because a path spec may be in error. I am sorry to bother you with this request but I am hoping someone will take pity on me and give me a little advise. Thanks BACKGROUND When I enter "M-x slime" in emacs, the following message appears: apply: Specified program for new process is a directory Emacs: GNU Emacs 21.3.50.2 (powerpc-apple-darwin7.0.0) of 2003-11-14 on marx.local Snippit from .emacs (setq inferior-lisp-program "/Applications/Emacs.app/Contents/Resources/share/emacs/21.3.50/lisp") (add-to-list 'load-path "/Users/robo2/Lisp/slime") (require 'slime) (add-hook 'lisp-mode-hook (lambda () (slime-mode t))) (add-hook 'inferior-lisp-mode-hook (lambda () (inferior-slime-mode t))) OpenMCL: Welcome to OpenMCL Version (Beta: Darwin) 0.14.1-p1! Command "openmcl" launches interpreter. Slime: robo2:~/lisp/slime/CVS robo2$ less Entries /ChangeLog/1.343/Wed Apr 21 22:58:34 2004// /HACKING/1.5/Mon Mar 29 00:59:38 2004// /README/1.9/Tue Nov 25 00:22:36 2003// /hyperspec.el/1.2/Thu Dec 4 16:42:53 2003// /metering.lisp/1.1/Wed Feb 18 07:25:38 2004// /nregex.lisp/1.1/Wed Apr 21 18:55:24 2004// /slime.el/1.271/Wed Apr 21 22:59:04 2004// /swank-allegro.lisp/1.29/Wed Apr 7 16:35:20 2004// /swank-backend.lisp/1.43/Wed Apr 14 18:50:36 2004// /swank-clisp.lisp/1.29/Tue Apr 6 10:42:53 2004// /swank-cmucl.lisp/1.97/Wed Apr 21 19:46:40 2004// /swank-gray.lisp/1.5/Tue Mar 9 19:35:36 2004// /swank-lispworks.lisp/1.38/Sat Mar 27 21:17:36 2004// /swank-loader.lisp/1.21/Wed Apr 21 18:56:42 2004// /swank-openmcl.lisp/1.72/Tue Apr 6 10:42:53 2004// /swank-sbcl.lisp/1.83/Tue Apr 6 10:42:53 2004// /swank-source-path-parser.lisp/1.5/Mon Mar 29 17:49:38 2004// /swank.asd/1.2/Thu Jan 22 00:10:39 2004// /swank.lisp/1.170/Wed Apr 21 21:51:23 2004// /test-all.sh/1.1/Tue Mar 9 20:12:43 2004// /test.sh/1.6/Sat Jan 31 11:50:25 2004// /xref.lisp/1.1/Fri Jan 2 08:17:15 2004// System: Mac OS X v 10.3.3 -- Dual 2 GHz PowerPC G5

6 8

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 23 Apr '04

23 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.343 slime/ChangeLog:1.345 --- slime/ChangeLog:1.343 Wed Apr 21 18:58:34 2004 +++ slime/ChangeLog Thu Apr 22 17:43:34 2004 @@ -1,3 +1,17 @@ +2004-04-22 Edi Weitz <edi(a)agharta.de> + + * slime.el (slime-read-system-name): Perform completion on all + systems in the central registry. + + * swank.lisp (list-all-systems-in-central-registry): New function. + +2004-04-22 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-repl-update-banner): Add workaround to force the + proper behavior of the the first command in the REPL buffer. + (slime-repl-shortcut-history): Define the variable to make XEmacs + happy. + 2004-04-22 Tiago Maduro-Dias <tcmd(a)rnl.ist.utl.pt> * slime.el (slime-space): Cleanup.

1 0

[slime-devel] slime-read-system-name
by Edi Weitz 22 Apr '04

22 Apr '04

Here's a patch to allow for completion in shortcut operations which deal with ASDF systems. It's sub-optimal because it only checks ASDF's central registry but I don't think it's possible to write a general solution in the presence of ASDF:*SYSTEM-DEFINITION-SEARCH-FUNCTIONS*. I was about to write that I doubt anybody uses custom search functions anyway and that I myself had never heard of them. But then I remembered that I had: <http://weitz.de/asdf-install/#load-asdf-install> :) Anyway, here's the patch. Cheers, Edi.

2 3

Re: [slime-devel] errors on startup
by Helmut Eller 22 Apr '04

22 Apr '04

Artem Baguinski <artm(a)v2.nl> writes: > plus this *Compile-Log* buffer flushed for a split second. > I understand that warning is something to expect in a alpha version > of the software, but i still suspect i'm doing something > wrong... e.g. compiling slime every time i (require) it. could that > be helped? We byte-compile some performance critical functions at load time, this is why you see the warnings every time. I don't see the warnings, tough. Neither in CVS Emacs nor in Emacs 20. Could you find out which functions cause the warnings? Just byte-compile the file and press RET in the *Compile-Log* buffer over the warning. Helmut.

2 3

[slime-devel] hyperspec-addon.el
by Edi Weitz 22 Apr '04

22 Apr '04

In case you haven't seen this on c.l.l: <http://homepage1.nifty.com/bmonkey/emacs/elisp/hyperspec-addon.el> I think it should be added to SLIME. Edi.

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel