From: Evan Aad <oddeveneven@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Eager macro-expansion failure
Date: Sun, 6 Nov 2022 12:17:02 +0200 [thread overview]
Message-ID: <CA+-Lr-CxmPF=e-MckTrOhc9p5U6m4B-jbBv121_sTkZ4MXY2kg@mail.gmail.com> (raw)
In-Reply-To: <87tu3cv3zq.fsf@gnu.org>
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
>
next prev parent reply other threads:[~2022-11-06 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 7:13 Eager macro-expansion failure Evan Aad
2022-11-06 8:58 ` Tassilo Horn
2022-11-06 10:17 ` Evan Aad [this message]
2022-11-07 6:05 ` Tassilo Horn
2022-11-07 6:26 ` Evan Aad
-- strict thread matches above, loose matches on Subject: below --
2022-11-06 5:47 Evan Aad
2022-11-05 9:15 Evan Aad
2022-11-05 6:54 Evan Aad
2022-11-04 8:51 Evan Aad
2022-11-04 11:34 ` Eli Zaretskii
2022-11-04 11:43 ` Evan Aad
2022-11-04 12:10 ` Eli Zaretskii
2022-11-04 13:12 ` Evan Aad
2022-11-04 13:49 ` Eli Zaretskii
2022-11-04 18:46 ` Evan Aad
2022-11-04 8:24 Evan Aad
2022-11-04 15:51 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-04 6:01 Evan Aad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+-Lr-CxmPF=e-MckTrOhc9p5U6m4B-jbBv121_sTkZ4MXY2kg@mail.gmail.com' \
--to=oddeveneven@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).