slime on github
Paul Bowyer
pbowyer at olynet.com
Mon Jan 27 19:36:28 UTC 2014
On 01/27/2014 10:48 AM, João Távora wrote:
> Paul Bowyer <pbowyer at olynet.com> writes:
>
>> I tried exactly what you said and when I entered
>> (sb-ext:describe-compiler-policy) in the *inferior lisp* buffer, the
>> output from that command showed up in the REPL, not in the *inferior
>> lisp* buffer where I thought it should go.
I did C-x 2 to get two buffers and then in the lower buffer I did C-x
C-left-arrow to change it to *inferior lisp*.
Then I entered (sb-ext:describe-compiler-policy) and all of the output
from that command went to the upper
buffer *slime-repl sbcl*.
This is with the .emacs you sent.
>> Also, I can no longer clear the *inferior lisp* buffer by selecting
>> everything and pressing the Delete key, which I was able to do with my
>> original .emacs file.
More on this: If I select everything in the *inferior lisp* buffer and
use the edit>cut menu selection,
then it deletes everything in the *inferior lisp* buffer, but I cannot
do it with the delete key.
This is with the .emacs you sent.
> This I can't reproduce, at least not with emacs -Q.
When I do emacs -Q from a command prompt, Emacs opens with only 2
buffers, *scratch* and *Messages*. I cannot do M-x slime because it
comes back with [no match].
This is with the .emacs you sent.
>
> That is the thing: can you or can you not reproduce the issue with a
> clean "emacs -Q" run? Either that or moving your .emacs to the side
> should do the trick.
Can't use emacs -Q to test anything with slime...
>
> The fix I just pushed fixes *a* "error in process filter" bug in
> slime-repl-emit, in the situation I describe in the commit message, but
> I still cannot reproduce the behaviour you describe. Commands issues in
> the *inferior lisp* buffer output to that buffer, output does not go to
> the REPL buffer that the slime-repl.el contrib creates.
I'll upgrade my slime to see how it acts...
>
>> My Emacs is a package that comes with Linux Mint 14 and looks like it
>> originated with Debian. The startup page shows:
>> "This is GNU Emacs 23.4.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.12)
>> of 2012-09-22 on allspice, modified by Debian"
>> There might be something non-standard about my Emacs-23 package...
> I don't think so, I'm using Debian at home as well, as it also says
> "modified by Debian"
>
>> There must be something going on with my original .emacs file that was
>> causing the problem with the error messages. Rather than having you
>> look at it, I'll fiddle with it using what you sent as the starting
>> point and add things a little at a time to see where the error occurs.
> I'd have no problems if you send me the file.
I'm attaching a copy of my original .emacs file (emacs.save)
>
> João
>
By the way, yesterday I upgraded my sbcl to sbcl-1.1.14 which shouldn't
matter to slime, but I'm just letting you know.
Thanks,
Paul Bowyer
-------------- next part --------------
;; Modified to track down error messages when loading slime-github
;;Don't know what this does, but I saw it in slime/README.md so I thought to try it...
```el
(filesets-init) ;;Added to allow fileset usage
(require 'cl-lib "~/my-slime-sandbox/slime/lib/cl-lib.el") ;;this is cl-lib-0.3 shipped w/slime.
;;Latest slime installation
(add-to-list 'load-path "~/my-slime-sandbox/slime/") ;your SLIME directory
;;Stuff from http://archgeek.wordpress.com/2009/02/07/setting-up-slime-emacs-and-sbcl/
(eval-after-load "slime"
'(progn
;;Recently added these three lines to allow quicklisp to work
(set-language-environment "UTF-8")
(setq slime-net-coding-system 'utf-8-unix)
;;(load (expand-file-name "~/quicklisp/slime-helper.el")) ;;NOTE: this causes quicklisp to load its version of slime rather than mine
(setq slime-lisp-implementations
'(
(sbcl ("/usr/local/bin/sbcl") :coding-system utf-8-unix) ;;for sbcl
;;cmucl won't load clx under mcclim!
;;(cmucl ("/opt/cmucl-20d/bin/lisp") :coding-system iso-8859-1-unix) ;;Not using
;;;;(cmucl ("/opt/cmucl-20d/bin/lisp") :coding-system utf-8-unix) ;;Don't work
;;(ccl ("/usr/local/bin/ccl") :coding-system utf-8-unix) ;;Not using
;;(abcl ("/home/pfb/abcl")) ;;Not using
;;(ecl ("/usr/local/ecl32/bin/ecl") :coding-system utf-8-unix) ;;Not using
;;;;(clforjava ("/home/pfb/clforjava")) ;;Doesn't work properly
;;;;(clisp ("/usr/bin/clisp")) ;;Not using
)
common-lisp-hyperspec-root "~/my-slime-sandbox/HyperSpec/")
(slime-setup '(
slime-fancy ;;added this when quicklisp was added
slime-tramp ;;added this when quicklisp was added. (may be useful)
slime-asdf
;;slime-typeout-frame ;;starts slime with a external typeout frame
slime-indentation
slime-mdot-fu
;;slime-sbcl-exts ;;decided not to continue with this
slime-xref-browser
slime-highlight-edits ;;Added this one
))
;; Remove the following without noticed problems
;;(slime-autodoc-mode)
;;(setq slime-complete-symbol*-fancy t)
;;(setq slime-complete-symbol-function 'slime-fuzzy-complete-symbol)
;;(add-hook 'lisp-mode-hook (lambda () (slime-mode t)))
;;The following two lines are causing error messages in the slime message buffer
;;find another logger!
;;(load "~/quicklisp/log4slime-setup.el")
;;(global-log4slime-mode 1) ;;This generates a compiler warning
))
(require 'slime-autoloads)
(custom-set-variables
;; custom-set-variables was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
'(tab-width 4) ;;this works
'(cua-mode t nil (cua-base))
'(double-click-time 750)
'(filesets-data (quote (("math-stuff" (:pattern "~/Documents/LispCode/Mathstuff" "^.+\\.lisp$")) ("clx-gui-classes" (:pattern "~/Documents/LispCode/clx-gui-classes" "^.+\\.lisp$")) ("mpfr-cffi-library" (:pattern "~/Documents/LispCode/MPFRstuff" "^.+\\.lisp$")) ("Actor-stuff" (:pattern "~/Documents/LispCode/Actors" "^.+\\.lisp$")))))
'(mouse-drag-copy-region nil)
'(show-paren-mode t))
(custom-set-faces
;; custom-set-faces was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
'(fringe ((((class color) (background light)) (:background "white" :foreground "black")))))
More information about the slime-devel
mailing list