unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 01:09:24 +0100	[thread overview]
Message-ID: <87bky4m897.fsf@web.de> (raw)
In-Reply-To: <87fsngm952.fsf@web.de> (Michael Heerdegen's message of "Fri, 18 Mar 2022 00:50:17 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Here is the issue:
>
> https://github.com/jwiegley/emacs-async/issues/153

For now I gave the advice to print symbols with `print-symbols-bare'
bound to t...

> byte-optimize--dynamic-vars ->
> (#<symbol original-date at 24141> #<symbol number at 24125>)

... and leave it to you to decide if this should be fixed.  It's not a
big surprise to find symbols with positions in an internal variable of
the byte compiler.  If the position information is of no relevance in
that variable, I guess you can strip the positions?

BTW, async-bytecomp just compiles files in another Emacs instance for
better speed.  The concept is really simple.  It only informs the other
instance of some variable bindings it needs to know
(e.g. default-directory and load-path) - and
`byte-optimize--dynamic-vars' is one of them.  The values are being
printed in the original session and `read' and assigned in the slave
instance.

Michael.





  reply	other threads:[~2022-03-18  0:09 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 [this message]
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=87bky4m897.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).