-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
wrong-type-argument stringp (package-delete . 3) #1613
Comments
This gives me no error with latest Swiper checkout a05b2bc and Emacs versions
and
The error you are getting sounds like those in #1565 and #1567, which were supposed to be fixed by #1568. Have you tried reinstalling Ivy to make sure you include that fix? If you already have the fix in #1568, then I suspect a bug in |
I reinstalled |
This is happening to me to as well. Could it be something in 4e3eaf4? |
I'm currently AFK, but if you're sure it's not the doing of |
I'll hopefully get a chance to look at this before 01:00 UTC+3, if no-one beats me to it. |
I saw that commit and hadn't heard of amx so I gave it a try but now that's coming up. I've reverted to the previous version of |
Hi: |
Yes, I can confirm it is related to the latest |
I found a solution, the problem was that we were using the amx-cache that has the same format than smex-cache, but the ivy-read expects just a list of strings like smex-ido-cache; but this variable was deleted in amx. So I propose to do the formatting on the fly. |
@Ergus thanks, just merged. |
No,
The problem lies in the default Lines 872 to 873 in 1355542
Here, the type and value of (ivy-read "" '((a . 1)
(b . 2)
(c . 3))
:action (lambda (x)
(message "`%S'" x))) prints |
@basil-conto Thanks for the insight. |
Document return value format and reformat amx-cache transformation. Re: abo-abo#1613, abo-abo#1614, abo-abo#1615
Hi,
with latest
ivy/counsel/swiper
from MELPA, if I do M-x package-delete RET, I get this:Some details about my environment:
The same command works if I do:
emacs -Q
The text was updated successfully, but these errors were encountered: