From: Michael Heerdegen <michael_heerdegen@web.de>
To: 53678@debbugs.gnu.org
Cc: acm@muc.de, shuguang79@qq.com, monnier@iro.umontreal.ca
Subject: bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows
Date: Sun, 06 Feb 2022 05:08:28 +0100 [thread overview]
Message-ID: <875ypsmybn.fsf@web.de> (raw)
In-Reply-To: <tencent_9DDA7528CE8FAC3EE0295365BA0FFEB47307@qq.com> (Shuguang Sun via's message of "Sun, 06 Feb 2022 10:19:44 +0800")
Shuguang Sun via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
> No "#<" in the elc.
>
> A reproducible example is:
> - Install package `async` which includes `async-bytecomp`
> - M-x list-package
> - M-x async-bytecomp-package-mode (make sure
> `async-bytecomp-package-mode` is enabled)
> - M-x package-reinstall <= `magit`
Maybe it appears in the communication with the other Emacs instance?
Michael.
prev parent reply other threads:[~2022-02-06 4:08 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ypsmybn.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=53678@debbugs.gnu.org \
--cc=acm@muc.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.