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 working with list expressions in the minibuffer, if I have a set of parenthesis (), and the cursor is inside the expression, sp-unwrap-sexp should unwrap the expression.
Actual behavior
sp-unwrap-sexp throws a (wrong-type-argument stringp nil)
Steps to reproduce the problem
Eval an elisp expression in the minibuffer
Enter an empty expression ()
Move the cursor inside the parenthesis
Try sp-unwrap-sexp
Backtraces if necessary (M-x toggle-debug-on-error)
In recent enough smartparens you can call M-x sp-describe-system to generate this report. Please fill manually what we could not detect automatically. Edit the output as you see fit to protect your privacy.
smartparens version: 20230225.1026
Active major-mode: minibuffer
Emacs version (M-x emacs-version): GNU Emacs 28.2 (build 1, aarch64-apple-darwin21.1.0, NS appkit-2113.00 Version 12.0.1 (Build 21A559)) of 2022-09-12
Expected behavior
When working with list expressions in the minibuffer, if I have a set of parenthesis
()
, and the cursor is inside the expression,sp-unwrap-sexp
should unwrap the expression.Actual behavior
sp-unwrap-sexp
throws a(wrong-type-argument stringp nil)
Steps to reproduce the problem
()
sp-unwrap-sexp
Backtraces if necessary (
M-x toggle-debug-on-error
)Environment & version information
In recent enough
smartparens
you can callM-x sp-describe-system
to generate this report. Please fill manually what we could not detect automatically. Edit the output as you see fit to protect your privacy.smartparens
version:20230225.1026
M-x emacs-version
):GNU Emacs 28.2 (build 1, aarch64-apple-darwin21.1.0, NS appkit-2113.00 Version 12.0.1 (Build 21A559)) of 2022-09-12
Lead and Potential Resolution
I think that
thing-at-point
is returningnil
in the minibuffer for whatever reason insp--unwrap-sexp
on these lines.I have no idea if this is expected behaviour for
thing-at-point
in this context. If it is, then there probably needs to be a check like the following:While this eliminates the error me, if
thing-at-point
is not supposed to returnnil
in this situation, then this might not be the right solution.The text was updated successfully, but these errors were encountered: