Re: Eager macro-expansion failure

[Evan Aad]

Thanks Tassilo.

I've followed your advice and updated my list of packages. At the end
of the update the following message appeared in the very bottom of the
Emacs window:

> Wrong type argument: listp, async

What does this message mean? Does it indicate there's an issue that
requires resolution in order for Emacs to work properly and as
expected? If so, how can I resolve this issue?

> Hi Evan,
>
> I've not read the complete thread but I've seen errors like that from
> time to time.  The problem seems to be incompatibilities in emacs
> byte-code, e.g., byte-code produced by emacs version X is not compatible
> with that produced by emacs version Y.  It should be compatible when X
> is smaller than Y but not when it's the other way round.  So such
> problems are to be expected especially when switching to a newer emacs
> version, installing some package with it, and then switching back to
> some older version.
>
> Usually, those problems can be fixed by recompiling packages and there's
> a new command `package-recompile-all' in the current development version
> (going to be emacs 29) making that very easy to do.
>
> > So the culprit is the projectile package; specifically
> > projectile-20180107.2233
>
> Is there a reason you are using such an ancient version?  Don't you
> update your packages from time to time?  Again, the current emacs
> development version has a nice `package-update-all' command making that
> easy.
>
> > Could anyone please help me proceed from here to resolve whatever
> > problem causes the error message?
>
> For the time being, you have to do M-x list-packages RET, hit U in the
> packages buffer to mark updatable package, and then hit x to start the
> update.  That will most probably also fix you issue as projectile is
> certainly a package which has an updated version available.
>
> But note that an update after 4 years might bring other surprises, of
> course.
>
> Bye,
> Tassilo
>