[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[nongnu] elpa/sly 0b48543: Fix #423: don't accidentally load slime.el in
From: |
ELPA Syncer |
Subject: |
[nongnu] elpa/sly 0b48543: Fix #423: don't accidentally load slime.el in far-fetched scenarios |
Date: |
Wed, 3 Mar 2021 05:57:09 -0500 (EST) |
branch: elpa/sly
commit 0b485431856592ca9a2265ccda1b9030ad1e3119
Author: João Távora <joaotavora@gmail.com>
Commit: João Távora <joaotavora@gmail.com>
Fix #423: don't accidentally load slime.el in far-fetched scenarios
In some contorted cases it was possible to have Lisp buffers open but
slime.el not loaded yet, and only setup as autoloads. Then loading
sly.el would inadvertently trigger loading slime.el, presumably
undesired.
Thanks to Olivier Certner for the report.
* sly.el [top]: Check for (featurep 'slime) before (funcall 'slime-mode -1)
---
sly.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sly.el b/sly.el
index 37567c3..36dbceb 100644
--- a/sly.el
+++ b/sly.el
@@ -7464,7 +7464,7 @@ and replace `sly-editing-mode' with
`slime-lisp-mode-hook'.")))
(with-current-buffer buffer
(when (eq major-mode 'lisp-mode)
(sly-editing-mode 1)
- (ignore-errors (funcall 'slime-mode -1))))))
+ (ignore-errors (and (featurep 'slime) (funcall 'slime-mode -1)))))))
(t
(warn
"`sly.el' loaded OK. To use SLY, customize `lisp-mode-hook' and remove
`slime-lisp-mode-hook'.")))
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [nongnu] elpa/sly 0b48543: Fix #423: don't accidentally load slime.el in far-fetched scenarios,
ELPA Syncer <=