You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using sly-describe-symbol, it will use builtin describe in backend. However, if describing a list with tons of data (in my case, a 34MB in text), this will break the SLY connection (or crash Emacs).
I change the documentation function to something like this:
(let ((type (plist-get candidate :icon))
(key (plist-get candidate :key)))
(pcase type
((or"function""method""operator")
(sly-eval `(slynk:describe-function ,key)))
;; use slynk-apropos::briefly-describe-symbol-for-emacs;; for variable (make sure it won't print too much of its value).
((or"variable")
(sly-eval
`(slynk::with-buffer-syntax
()
(cl:format cl:nil "~A"
(cl:getf (slynk-apropos::briefly-describe-symbol-for-emacs
(slynk::parse-symbol-or-lose ,key) cl:nil)
:variable)))))
(_
(sly-eval `(slynk:describe-symbol ,key))))
which use slynk-apropos::briefly-describe-symbol-for-emacs and it was fine to use.
I wander if there's some way to make it more neatly.
The text was updated successfully, but these errors were encountered:
When using
sly-describe-symbol
, it will use builtindescribe
in backend. However, if describing a list with tons of data (in my case, a 34MB in text), this will break the SLY connection (or crash Emacs).I change the documentation function to something like this:
which use
slynk-apropos::briefly-describe-symbol-for-emacs
and it was fine to use.I wander if there's some way to make it more neatly.
The text was updated successfully, but these errors were encountered: