From: Michael Heerdegen <michael_heerdegen@web.de>
To: Alan Mackenzie <acm@muc.de>
Cc: 54433@debbugs.gnu.org
Subject: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp
Date: Fri, 18 Mar 2022 00:50:17 +0100 [thread overview]
Message-ID: <87fsngm952.fsf@web.de> (raw)
In-Reply-To: <YjMbUTKNbcLxKVC1@ACM> (Alan Mackenzie's message of "Thu, 17 Mar 2022 11:28:17 +0000")
Alan Mackenzie <acm@muc.de> writes:
> Could you please give a recipe for this situation, preferably starting
> from emacs -Q? I don't know how to use async-bytecomp.el, for
> example.
Here is the issue:
https://github.com/jwiegley/emacs-async/issues/153
But I don't think async or async-bytecomp is related to this issue at
all. It only hits an issue with vanilla Emacs. I think it's not
necessary for you to have a look at async, unless you are interested,
also because I have a recipe for emacs -Q:
Byte compile lisp/calendar/appt.el (I did that with B from dired); after
that:
byte-optimize--dynamic-vars ->
(#<symbol original-date at 24141> #<symbol number at 24125>)
The problem for async-bytecomp is then only that a result like this is
not `read'able after being printed.
Thierry has removed that variable from the list of handled variables for
now which circumvents the problem.
Michael.
next prev parent reply other threads:[~2022-03-17 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 2:55 bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Michael Heerdegen
2022-03-17 11:28 ` Alan Mackenzie
2022-03-17 23:50 ` Michael Heerdegen [this message]
2022-03-18 0:09 ` Michael Heerdegen
2022-03-18 11:58 ` Alan Mackenzie
2022-03-18 13:37 ` Thierry Volpiatto
2022-03-18 21:28 ` Alan Mackenzie
2022-03-19 6:17 ` Thierry Volpiatto
2022-03-24 1:38 ` 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=87fsngm952.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=54433@debbugs.gnu.org \
--cc=acm@muc.de \
/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).