unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: 54433-done@debbugs.gnu.org, Alan Mackenzie <acm@muc.de>
Subject: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp
Date: Thu, 24 Mar 2022 02:38:14 +0100	[thread overview]
Message-ID: <87fsn8ku49.fsf@web.de> (raw)
In-Reply-To: <87pmmi5uj9.fsf@posteo.net> (Thierry Volpiatto's message of "Sat,  19 Mar 2022 06:17:36 +0000")

Thierry Volpiatto <thievol@posteo.net> writes:

> > I think that all the byte-* variables are connected with byte
> > compilation.  But I also think that they are (?nearly?) all internal
> > variables, so it shouldn't be needed to copy them to an aynchronous
> > thread (?or process?).
>
> Thanks to confirm this.

I can confirm that the problem has been fixed well in the "async"
package, and we have found that everything in Emacs is working as
expected.  So I'm closing this report.  Thanks to everybody involved!

Michael.





      reply	other threads:[~2022-03-24  1:38 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
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 [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

  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=87fsn8ku49.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=54433-done@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=thievol@posteo.net \
    /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).