all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 54433@debbugs.gnu.org, acm@muc.de
Subject: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp
Date: Thu, 17 Mar 2022 11:28:17 +0000	[thread overview]
Message-ID: <YjMbUTKNbcLxKVC1@ACM> (raw)
In-Reply-To: <87a6dpnv8g.fsf@web.de>

Hello, Michael.

Thanks for the bug report.

On Thu, Mar 17, 2022 at 03:55:27 +0100, Michael Heerdegen wrote:

> Hello,

> when updating packages with M-x package-list-packages, and using
> async-bytecomp.el to compile, some users get an error like this one:

> error in process sentinel: async-when-done: Invalid read syntax: "#<"
> error in process sentinel: Invalid read syntax: "#<"

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.

> This seems to be related to the recent addition of symbols with
> positions.

It sounds like something is storing a compiler intermediate form, and
reading it again with the reader.

> async uses `async-inject-variables' to collect variable bindings of
> interest and deliver them to the other Emacs instance.  The return value
> contains symbols with positions in some scenarios.

> The root of the trouble seems to be the value of
> `byte-optimize--dynamic-vars'.  As soon as I byte compile any file, I
> see lots of symbols with positions in `byte-optimize--dynamic-vars'.

Thanks, that should be useful information.

> Is that expected?  What has to be done?

No, it is not expected.  As for what needs doing, let's just say I
wasn't aware of the existence of async-bytecomp.el a day or two ago.
;-(

> TIA,

> Michael.


> In GNU Emacs 29.0.50 (build 55, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
>  of 2022-03-17 built on drachen
> Repository revision: 97e687006498490cca1e6dabc1ea7e692271c5ed
> Repository branch: master
> Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
> System Description: Debian GNU/Linux 11 (bullseye)

> Configured using:
>  'configure --with-native-compilation --with-xwidgets'

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2022-03-17 11:28 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 [this message]
2022-03-17 23:50   ` Michael Heerdegen
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YjMbUTKNbcLxKVC1@ACM \
    --to=acm@muc.de \
    --cc=54433@debbugs.gnu.org \
    --cc=michael_heerdegen@web.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 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.