From: Alan Mackenzie <acm@muc.de>
To: Shuguang Sun <shuguang79@qq.com>
Cc: 53678 <53678@debbugs.gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows
Date: Thu, 3 Feb 2022 19:16:23 +0000 [thread overview]
Message-ID: <YfwqB2nTCYUmVTN0@ACM> (raw)
In-Reply-To: <tencent_3EAC03736A6441008F99B2D395F2BF9DFB0A@qq.com>
Hello again, Shuguang.
On Thu, Feb 03, 2022 at 10:55:02 +0800, Shuguang Sun wrote:
> Thank you Stefan and Alan in another email.
> With the hint, I find out the `async-bytecomp-package-mode` is turn on
> by the package `helm-core`. So it is a bug of `async-bytecomp` maybe,
> and I will report it the package author.
> Sorry for the misleading information in the orignial email.
A hypothesis for what is happening is that a symbol with position,
looking like:
#<symbol foo at 666>
, has somehow got into a .elc file. The loader (contained within the
file .../src/lread.c) chokes when it encounters such a symbol.
If you have an idea which .elc file might be causing the trouble, could
I suggest you visit this file within Emacs. There is a mode for .elc
files. :-). Then search the buffer for the string "#<symbol". Or even
just for the "#<" which the loader might have reported.
> 发自我的iPhone
> ------------------ Original --------------
> Date: Wed,Feb 2,2022 11:32 AM
> Eli Zaretskii [2022-02-01 17:00:34] wrote:
> >> Date: Tue, 01 Feb 2022 13:32:11 +0800
> >> From: Shuguang Sun via "Bug reports for GNU Emacs,
> >> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >> When I try to install packages from the Package Menu or the command of
> >> package-install since about two weeks ago, it reports the error:
> >> ```
> >> error in process sentinel: async-when-done: Invalid read syntax: "#<"
> >> error in process sentinel: Invalid read syntax: "#<"
> >> ```
> > Stefan, any thoughts?
> IIUC the above error involves some part of the `async` package.
> Could you give a bit more information about how you hooked `async` with
> `package`?
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-02-03 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 5:32 bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-01 15:00 ` Eli Zaretskii
2022-02-01 19:00 ` Arash Esbati
2022-02-02 3:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <yjinleyvp2xw.fsf@qq.com>
2022-02-01 20:15 ` Alan Mackenzie
2022-03-24 1:03 ` Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-24 1:31 ` Michael Heerdegen
2022-02-03 2:55 ` Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 19:16 ` Alan Mackenzie [this message]
2022-02-06 2:19 ` Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-06 4:08 ` Michael Heerdegen
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=YfwqB2nTCYUmVTN0@ACM \
--to=acm@muc.de \
--cc=53678@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=shuguang79@qq.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).