-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error: Wrong type argument stringp" in Emacs 29.1 #130
Comments
What version of Emacs are you on? Could you try reproducing it with
(steps adapted from #88 ) |
I'm on Emacs 29.1. Here's the symex-specific output when running
|
Great, thanks for the detailed report! I'm returning to working on Symex in the coming weeks and will look into this soon. |
I have the same errors (29.3) |
@zilti @Doodler8888 If you |
Since my last comment, i've changed my emacs configuration considerably. The most noticeable changes are going to the main branch instead of 29.3 and changing elpaca in favor of straight because elpaca started giving me compilation errors on other packages. After your answer i've tried to reinstall symex again and now i don't get the errors. I suppose it might be something with elpaca. But i haven't tried to trace or debug anything, so i don't really know what helped me.
|
Thanks for checking! @zilti How about you, I notice your errors also mention elpaca. Any chance you're still seeing the error? |
I'm seeing these errors with Symex (including with the minimal I'm running Emacs 29.4 under Arch Linux. |
This minimal config fixes the issue for me (although likely not the underlying cause): (require 'package)
(add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t)
(package-initialize)
(use-package symex
:ensure t
:init
(add-to-list
'native-comp-jit-compilation-deny-list
"/symex-")
:config (symex-initialize)
:bind ("s-;" . symex-mode-interface)) |
Thanks for reporting @TamsynUlthara ! Is it only I recently commented on another issue regarding these warnings, I'll quote that here for context:
Another thing is, these byte compilation warnings don't provide a lot of information on tracking the source of the error. E.g. in the |
The automatic compilation from Emacs seems to trigger some warnings that pop up every time I start Emacs:
The text was updated successfully, but these errors were encountered: