[cl-debian] Bug#340442: cl-swank: Removing package leaves variable slime-backend set
Package: cl-swank Severity: normal 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" -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
On Wednesday 23 November 2005 15:05, Nicolas Neuss wrote:
Package: cl-swank Severity: normal
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? Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|
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
Your message dated Fri, 28 Jul 2006 13:49:13 +0200 with message-id <200607281349.16591.pvaneynd@debian.org> and subject line closing old and unreproducible bugs has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
participants (4)
-
Luca Capello -
Nicolas Neuss -
owner＠bugs.debian.org -
Peter Van Eynde