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

[slime-devel] Re: Putting REPL prompt on the mode line?
by bdowning＠lavos.net 30 Dec '05

30 Dec '05

On Wed, Dec 21, 2005 at 07:54:10PM -0800, Derek Peschel wrote: > >More importantly to me, the prompt tells me "this is what *PACKAGE* was > >when I ran this command n {minutes,hours,days} ago." I'd be very > >unhappy for that information to go away. > > I wodnered if that issue would come up. If the information was stored > as a property of the text region that contains the command, and displayed > on the mode line or something, would that work for you? My gut feeling is that putting more distance between the expression and the package it was run in is not a win for me. Plus you'd have to put point on it to determine it that way which is quite inconvenient. > Do you want to see that kind of prompt in an editor buffer or let the > editor take care of it? In a normal Lisp buffer I agree - its primary purpose is editing the file, and interaction with the Lisp is secondary. Having a buffer-package shown on the mode-line works well in that case. However, I think the REPL buffer is a different story - interaction is primary there, so I think the prompt works well (for me). > I'm going a step further and changing the way the package and evaluation > state are shown. It's purely for appearance. Would a REPL buffer be nicer > if the left margins of all lines of input and output were aligned? IMHO, no. I like having the input indented by the prompt because it helps delimit what exactly is input without relying on font faces. Please experiment, though. Just make the end product be a customize option and everyone will be happy. :-) -bcd

3 2

[slime-devel] XEmacs-nomule, slime cvs 20051202, sbcl 0.9.7
by Adam Fabian 30 Dec '05

30 Dec '05

Hi. I'm having trouble with the above configuration. I saw this thread: http://article.gmane.org/gmane.lisp.slime.devel/4367 http://article.gmane.org/gmane.lisp.slime.devel/4368 that looks like it might be the same or a related problem. I'm not really sure. Looked around the mailing list, did some web searching, I don't think this is a duplicate report. Anyway, if I try to M-x slime with XEmacs-nomule (which is what I normally use) I get: Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix bina (cuts off, I don't know how to read more of the minibuffer) as an error. If I try the mule version, which my distribution packages, I get a segmentation fault from XEmacs (this, of course, is probably better reported as an XEmacs bug, which I'm planning on doing.) This is XEmacs 21.4.17 with slime cvs 20051202 and sbcl 0.9.7. This is my first time trying to start things up. (That is to say, I had no working previous configuration.) I really don't know what to make of this, but here's what I get if I try it after setting debug-on-error to t: Debugger entered--Lisp error: (error "Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)") signal(error ("Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)")) cerror("Invalid slime-net-coding-system: %s. %s" nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)) apply(cerror "Invalid slime-net-coding-system: %s. %s" (nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix))) error("Invalid slime-net-coding-system: %s. %s" nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)) (if props nil (error "Invalid slime-net-coding-system: %s. %s" coding-system (mapcar ... slime-net-valid-coding-systems))) (unless props (error "Invalid slime-net-coding-system: %s. %s" coding-system (mapcar ... slime-net-valid-coding-systems))) (let ((props ...)) (unless props (error "Invalid slime-net-coding-system: %s. %s" coding-system ...)) (when (and ... ...) (assert default-enable-multibyte-characters)) t) slime-check-coding-system(nil) (let ((args ...)) (slime-check-coding-system coding-system) (when (or ... ...) (let ... ... ...))) (catch (quote --cl-block-slime-start--) (let (...) (slime-check-coding-system coding-system) (when ... ...))) (cl-block-wrapper (catch (quote --cl-block-slime-start--) (let ... ... ...))) (block slime-start (let (...) (slime-check-coding-system coding-system) (when ... ...))) (let* ((program ...) (program-args ...) (coding-system ...) (init ...) (name ...) (buffer ...)) (let (...) (while --keys--102022 ...)) (block slime-start (let ... ... ...))) slime-start(:program "/usr/local/bin/sbcl" :program-args nil) apply(slime-start (:program "/usr/local/bin/sbcl" :program-args nil)) (lambda (&optional command coding-system) "Start an inferior^_superior Lisp and connect to its Swank server." (interactive) (apply (function slime-start) (slime-read-interactive-args)))() call-interactively(slime) command-execute(slime t) execute-extended-command(nil) call-interactively(execute-extended-command)

3 2

[slime-devel] Problems with lambda-gtk + slime on windows/clisp
by Ignas Mikalajunas 28 Dec '05

28 Dec '05

Hi, what can i do to avoid emacs/slime freezing when running simple GTK examples on clisp ? I can run hello-world on a stand-alone clisp, yet whenever i am evaluating the function in emacs - slime just stops responding ... (no errors can be seen anywhere). I have tried fiddling with communication styles, yet non except "nil" were accepted. Maybe anyone had simmilar problems with SDL/LTK/wxCL? Ignas Mikalajunas

2 2

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 27 Dec '05

27 Dec '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.824 slime/ChangeLog:1.825 --- slime/ChangeLog:1.824 Thu Dec 22 17:06:49 2005 +++ slime/ChangeLog Tue Dec 27 16:14:44 2005 @@ -1,3 +1,13 @@ +2005-12-27 Helmut Eller <heller(a)common-lisp.net> + + Keep a history of protocol events for better bug reports. + + * swank.lisp (log-event): Record the event in the history buffer. + (*event-history*): Buffer for events. + (dump-event-history): New function. + (close-connection): Escape non-ascii strings and include the event + history in the error message. + 2005-12-22 Helmut Eller <heller(a)common-lisp.net> Make highlighting of modified text a minor mode. Also use

1 0

[slime-devel] Can't start slime (OS X 10.3, Slime 1.2.1, OpenMCL 1.0)
by Carl Tucker 27 Dec '05

27 Dec '05

Hi, I'm having a problem getting slime to work. I'm new to this, so I apologize if I'm doing something stupid. Here's what happens when I start emacs and type M-x slime I get a new buffer, called *inferior-lisp* which then outputs the following: (load "/Users/cfta/lisp/slime-1.2.1/swank-loader.lisp" :verbose t) (swank:start-server "/tmp/slime.2167" :external-format :iso-latin-1-uni x) Welcome to OpenMCL Version 1.0 (DarwinPPC32)! ? ;Loading #P"/Users/cfta/lisp/slime-1.2.1/swank-loader.lisp"... ;Loading #P"/Users/cfta/.slime/fasl/openmcl-1.0-darwin-powerpc/swank -backend.dfs\l"... ;Loading #P"/Users/cfta/.slime/fasl/openmcl-1.0-darwin-powerpc/nregex.dfsl"... ;Loading #P"/Users/cfta/.slime/fasl/openmcl-1.0-darwin-powerpc/metering.dfsl"... ;Compiling "/Users/cfta/lisp/slime-1.2.1/swank-openmcl.lisp"... ;Compiler warnings for "/Users/cfta/lisp/slime-1.2.1/swank-openmcl.lisp" : ; Unused lexical variable STREAM, in (MAKE-STREAM-INTERACTIVE (T)). ; Warning: Interface file #P"ccl:darwin-headers;libc;functions.cdb" does not exist. ; While executing: CCL::CDB-OPEN Read error between positions 8480 and 8595 in /Users/cfta/lisp/slime-1.2.1/ swank\-openmcl.lisp. > Error in process listener(1): Foreign function not found: DARWIN32::|tmpnam| > While executing: CCL::LOAD-EXTERNAL-FUNCTION > Type :POP to abort. Type :? for other options. 1 > then I'm stuck in the debugger. If I type :pop to abort, I'm able to use the inferior lisp buffer as a lisp interpreter. If I open a new buffer and try to write some code, the mode line says (Lisp Slime[Polling: XXX]) , where the polling number just counts up. Nothing ever happens. None of the compile macros work either- C-c C-c says "not connected." Is it a problem with the way I've set the system up? I tried to follow the instructions for installing Open MCL and Slime, but I'm not sure I completely understood what I was doing with either. Thanks.

2 2

[slime-devel] slime starting problems
by Peter Herth 24 Dec '05

24 Dec '05

Hi, I just tried to run newest cvs slime with sbcl 0.9.7 and aquamacs, and I am stuck with the error message: error in process filter: Wrong number of arguments: nil, 12 Anyone an idea whats the problem? Peter

1 1

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 22 Dec '05

22 Dec '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.823 slime/ChangeLog:1.824 --- slime/ChangeLog:1.823 Tue Dec 20 01:25:58 2005 +++ slime/ChangeLog Thu Dec 22 17:06:49 2005 @@ -1,3 +1,15 @@ +2005-12-22 Helmut Eller <heller(a)common-lisp.net> + + Make highlighting of modified text a minor mode. Also use + after-change-functions instead of rebinding all self-inserting + keys. + + * slime.el (slime-highlight-edits-mode): New minor mode. + (slime-self-insert-command): Deleted. + (slime-before-compile-functions): New hook to decouple edit + highlighting from compilation. + (slime-highlight-edits-face): Renamed from slime-display-edit-face. + 2005-12-20 Marco Baringer <mb(a)bese.it> When inspecting classes, methods and generic functions show all

1 0

[slime-devel] Weird Display Bug w/ open minibuffer
by Stefan Kamphausen 22 Dec '05

22 Dec '05

Hi, I just came across a really weird display bug: 1. Start Slime 2. start CMUCL 3. open a lisp file and type something until you want to complete sth (in this case I wanted to complete #\New to #\Newline and it didn't work, but that's another story). Just make sure that there is only one possible completion. 4. Now do something to invoke a minibuffer dialog (say C-x C-f) 5. Go back to your lisp file w/o finishing the dialog (in Xemacs I can just C-x o out of the dialog). 6. Hit M-TAB for the completion The result is that the message "[Sole completion]" doesn't show up in the echo area but in the last line of the buffer. And it disappears a few seconds later. I tried to get the same thing with hippie-expand in a cperl-mode-buffer but there the message showed up in the echo area. So maybe it's in Slime. It may be an XEmacs problem, sure, and it's not really that important that it really needs a fix. Agreed. It's funny and weird nevertheless and I thought I'd let you know. Regards, Stefan PS: Slime: CVS of yesterday with Peter's Patch applied XEmacs: 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid CMUCL: CMU Common Lisp CVS 19c 19c-release + minimal debian patches (19C) System: Gentoo Linux -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie

1 0

[slime-devel] Symbol's function definition is void: syntax-ppss
by Chisheng Huang 22 Dec '05

22 Dec '05

The message on the Subject line is printed once in the mini buffer for every character entered into the REPL buffer. This is annoying and makes it impossible to type fast. Best, -cph

3 3

[slime-devel] Putting REPL prompt on the mode line?
by dpeschel＠eskimo.com 22 Dec '05

22 Dec '05

As a first step toward my general goal of making a LISP interface that is designed for random-access displays rather than simulated Teletypes, I thought I would get the prompt out of REPL buffers and put the same information on their mode lines. A one-line change to sline.el prevents printing the prompt string, but then I notice that "Evaluation aborted" messages appear in bold. Probably the face used for input that has been completed is being used for the messages. Is there any complete spec for what can appear in REPL buffers, so I know what code needs to be changed? The one-line change is to slime-repl-insert-prompt (line 2642 in SLIME 1.2.1): < (prompt (format "%s> " (slime-lisp-package-prompt-string)))) --- > (prompt "")) The next problem is to put the information in the mode line or perhaps in the top pane that currently shows the port and process IDs. The standard prompt shows the current package. To the user, the prompt also means "evaluation of the last form (or initialiation) was aborted or is complete" as well as "the reader is expecting new input and is not in the middle of reading anything". Does SLIME have a notion of package change, evaluation completion or abortion, and reader state change as separate events? Does the SWANK protocol allow them to be sent as signals that don't depend on any particular text output also being sent to SLIME at the same time? Thanks for your help, -- Derek

2 1