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

Using ANSI colors?
by Ben Lambert 07 Jan '18

07 Jan '18

Hi there, I just posted an "Issue" on GitHub (https://github.com/slime/slime/issues/420 <https://github.com/slime/slime/issues/420>), and then saw in the README that questions are better directed to this list. I'm not sure how to search the email archives so I'm not sure if this has been asked before. The question (repeated from GitHub) is: I've wondered about this for a while. Is it possible to print with ANSI colors in a Slime repl buffer? If I load the cl-ansi-text library from Quicklisp (ql:quickload :cl-ansi-text), and I run (cl-ansi-text:yellow "yellow") in the Slime REPL the output is: "[33myellow[0m". When I run the same commands directly in an SBCL REPL, it prints as expected "yellow" in a yellow color. Is it possible to use ANSI colors in Slime? Or maybe there's some workaround? Thanks, Ben

2 4

finding an implementation of SWANK interface
by 73budden . 06 Jan '18

06 Jan '18

Hi! Maybe I'm missing something, but I don't know how do I find defimplementation of some definterface. E.g. I want to go to swank/backend:activate-stepping, but EMACS only sends me to definterface, and I have to grep for defimplementation. I don't know how should I handle this, but I added a simple defparameter into defimplementation form. Now, when I'm asking for definition of swank/backend:activate-stepping, I see two suggested source locations: (defvar swank/backend:activate-stepping) (defun swank/backend:activate-stepping) defun is for definterface, defvar is for defimplementation. This works at least in SBCL, I guess it is handy. Patch is attached. This may seem a bit ugly, but SBCL does not suggest a way to extend its definition database with new classes, so I see no good way to go. WBR, Budden

4 10

Getting the source file pathname
by Chaitanya Gupta 09 Dec '17

09 Dec '17

Hi, I need the path of the source file from which a particular form is loaded (similar to __FILE__ in C). Currently I have the following macros in place: (defmacro source-pathname () (let ((compile-file-pathname *compile-file-pathname*)) `(or ,compile-file-pathname (load-time-value *load-pathname*)))) (defmacro source-truename () (let ((compile-file-truename *compile-file-truename*)) `(or ,compile-file-truename (load-time-value *load-truename*)))) (defmacro source-directory () `(make-pathname :defaults (source-truename) :name nil :type nil)) This works fine when I use (LOAD ...), (LOAD (COMPILE-FILE ...)), slime-load-file or slime-compile-and-load-file. However it fails when I use slime-compile-defun, slime-eval-defun or slime-eval-last-expression. Shouldn't slime bind *compile-file-pathname*, *load-pathname*, etc. when these functions are run? Thanks, Chaitanya

2 3