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
throws error wrong-type-argument stringp nil, and it turns out it's the matched library-name that becomes nil unexpectedly during the process of finding the required libraries.
Further digging shows that, the first required library "cl-lib" is processed successfully. However, after matching the second required library, "macroexp", (match-string 1) seems to be invalidated (evaluates to nil instead of "macroexp") after the (syntax-ppss) call in
Interestingly, in debugger, if I stop right before line 92 and evaluate (syntax-ppss) manually from debugger, (match-string 1) would not be changed to nil after line 92, and the whole function call can be successful if such manual evaluation is done to "guard" each matched string. Adding a dummy (syntax-ppss) call before line 92, however, will only invalidates (match-string 1) even earlier. It seems that only the interactive evaluation from debugger could "guard" the match.
I could not make the debugger step into syntax-ppss to further understand what's happening.
As the file path suggests, my platform is "emacsmacport" 29.1 installed with Homebrew on macOS.
I'm running into a weird error with Elsa v20230621.1005 MELPA:
throws error
wrong-type-argument stringp nil
, and it turns out it's the matchedlibrary-name
that becomesnil
unexpectedly during the process of finding the required libraries.Further digging shows that, the first required library
"cl-lib"
is processed successfully. However, after matching the second required library,"macroexp"
,(match-string 1)
seems to be invalidated (evaluates tonil
instead of"macroexp"
) after the(syntax-ppss)
call inElsa/elsa-dependencies.el
Line 92 in f719e24
Interestingly, in debugger, if I stop right before line 92 and evaluate
(syntax-ppss)
manually from debugger,(match-string 1)
would not be changed tonil
after line 92, and the whole function call can be successful if such manual evaluation is done to "guard" each matched string. Adding a dummy(syntax-ppss)
call before line 92, however, will only invalidates(match-string 1)
even earlier. It seems that only the interactive evaluation from debugger could "guard" the match.I could not make the debugger step into
syntax-ppss
to further understand what's happening.As the file path suggests, my platform is "emacsmacport" 29.1 installed with Homebrew on macOS.
[1] For convenience, the link to cl-macs.el is https://github.com/emacs-mirror/emacs/blob/master/lisp/emacs-lisp/cl-macs.el
The text was updated successfully, but these errors were encountered: