Bug#340442: [cl-debian] Bug#340442: cl-swank: Removing package leaves variable slime-backend set

Luca Capello luca at pca.it
Thu Nov 24 14:13:19 UTC 2005


Hello!

On Thu, 24 Nov 2005 11:13:07 +0100, Peter Van Eynde wrote:
> On Wednesday 23 November 2005 15:05, Nicolas Neuss wrote:
>> I encountered problems using the SLIME package with SBCL.  Then I
>> wanted to switch to CVS Slime by removing the slime and cl-swank
>> packages.  Strangely, this did not work, because even after "emacs
>> -q" the variable slime-backend is still set to
>> "/usr/share/common-lisp/source/slime/swank-loader.lisp"
>
> I fear I cannot reproduce this. Can you find out where the
> slime-backend variable comes from?

Here:
=====
gismo:/home/luca# grep -r slime-backend /etc/emacs*
/etc/emacs/site-start.d/50slime.el:(setq slime-backend
gismo:/home/luca# 
=====

But what is strange is that it seems ok after a purging step:
=====
gismo:/home/luca# dpkg --purge slime cl-swank
(Reading database ... 105476 files and directories currently
installed.)
Removing slime ...
remove/slime: purging byte-compiled files for emacs-snapshot
remove/slime: purging byte-compiled files for emacs21
Purging configuration files for slime ...
Removing cl-swank ...

gismo:/home/luca# grep slime-backend /etc/emacs*
gismo:/home/luca# 
=====

Obviously, I checked that after the purging step `slime-backend' is
no more defined in GNU Emasc snapshot.

Probably a misconfigured /etc/emacs* ?

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20051124/88e86c39/attachment.sig>


More information about the Cl-debian mailing list