From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Thierry Volpiatto Newsgroups: gmane.emacs.bugs Subject: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Date: Fri, 18 Mar 2022 13:37:43 +0000 Message-ID: <87sfrfpejc.fsf@posteo.net> References: <87a6dpnv8g.fsf@web.de> <87fsngm952.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6841"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Michael Heerdegen , 54433@debbugs.gnu.org To: Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 18 14:56:08 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nVD5L-0001Yr-TY for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 18 Mar 2022 14:56:08 +0100 Original-Received: from localhost ([::1]:45048 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nVD5K-00037i-LX for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 18 Mar 2022 09:56:06 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:49412) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nVCnq-0007go-0z for bug-gnu-emacs@gnu.org; Fri, 18 Mar 2022 09:38:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34414) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nVCnp-0004Rd-OO for bug-gnu-emacs@gnu.org; Fri, 18 Mar 2022 09:38:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nVCnp-0002s0-LR for bug-gnu-emacs@gnu.org; Fri, 18 Mar 2022 09:38:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Thierry Volpiatto Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 18 Mar 2022 13:38:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54433 X-GNU-PR-Package: emacs Original-Received: via spool by 54433-submit@debbugs.gnu.org id=B54433.164761067411018 (code B ref 54433); Fri, 18 Mar 2022 13:38:01 +0000 Original-Received: (at 54433) by debbugs.gnu.org; 18 Mar 2022 13:37:54 +0000 Original-Received: from localhost ([127.0.0.1]:56544 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nVCni-0002re-CR for submit@debbugs.gnu.org; Fri, 18 Mar 2022 09:37:54 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:59721) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nVCnf-0002rQ-Vw for 54433@debbugs.gnu.org; Fri, 18 Mar 2022 09:37:53 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id C2549240101 for <54433@debbugs.gnu.org>; Fri, 18 Mar 2022 14:37:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1647610665; bh=U1WUeUGwYZKBXzO5J0AtvOpL6ZD4O+Ju5A7VdOyaqLE=; h=From:To:Cc:Subject:Autocrypt:Date:From; b=kOqVvEo/5be5AU3KLhLbZHnvwQoF0nDGq94TUEedEW1S2Jn8UXSNG8qVIfIDIw48R MPWTi1uPGsXlkovTty9qAEZoen0bBCeTGDHUz4UL8NZrrRxftUCwdC0Jm+R9RNHCMa pvfdVCPkjRS3EGU6zAhA2OgCW6eY57g1/ng4TNQ6cKKpVzX7bN0iEaoQpmKYjecUMC x2Rbbq6mtmvjNOuu8v7RzqNc+fs9EmrmgKZhqPBSPtSCeBPRsu8rPKQAUeCRTLyrgm nAKR2RmW7S8B0p/AJZV05rgoMGsEZhKb4GwuCIsK7C+Ui4/EBgnJMm7x1NLPMdpU7w vGfh0YEEQX6Ag== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4KKlSS3pnJz6tmY; Fri, 18 Mar 2022 14:37:44 +0100 (CET) Autocrypt: addr=thievol@posteo.net; prefer-encrypt=mutual; keydata= mQGNBF8ylcIBDADG+hy+zR6L4/vbdDDZuSaMmSrU3A5QZJpeBCvxTr7MpzzruZbhLPW1K3R6N2MA edi8Y+C8o27FVRIjpdbaKMGu9je7JV/TbUQYo3SOwCK1vM4LUn4V6ZLzSYkuiEt4eyMoiDdyvN0p kcK6P9x9DCetcEVszXzQg+yzCVrQ2hXWDXWT4M18EC3wtO7RHPouMqGiwBFhBAYErCqFWFxQHkfb tG/4yGyJ58rglb65O3qijjMWvYwcWZun9/7qm8Z4/4mHopmo2zgU+OrptnLSZfkZGz3Y7Uf452xQ GVq0Fv75NPvQru7y+DYVhuVXXyAmGxt+vf4rIiixMBbhKEPjcxEPAa2LTzex2IsTZR+QVG9uDnqC WcgaOEQ58fzXNvNhtwwF/Rgio2XWAJVdmFWS59/k9W58CIUSNKBMZh2XeGdEmtHvDtCxW3z6FJha 36RzOM3fMNNiAGdFZJA84gcdloJR+sHCDTTPT3784fjr+V8An7sI581NGFzkRQqPvEQCZbUAEQEA AbQSdGhpZXZvbEBwb3N0ZW8ubmV0iQHUBBMBCgA+FiEEI9twfRN7r3nig/xwDsVtFB0W75MFAl8y lcICGwMFCQPCZwAFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQDsVtFB0W75MB3QwAlTsVzFmr +S/tMKwwwOibjhNPi/OZiUC2AYfaqfVAiIHDT3RbzDe03sAJoomJkJnYVjGzQZwibCMO2+ITkMPV 2wvrd4CbgS1KCVbrltwcuK/nxPCBaHytOCZUIInnhJo5PE/h03K In-Reply-To: (Alan Mackenzie's message of "Fri, 18 Mar 2022 11:58:34 +0000") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:228547 Archived-At: Alan Mackenzie writes: > Hello, Michael. > > On Fri, Mar 18, 2022 at 00:50:17 +0100, Michael Heerdegen wrote: >> Alan Mackenzie 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 > > Thanks. I've read it, now. > >> 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 -> >> (# #) > >> The problem for async-bytecomp is then only that a result like this is >> not `read'able after being printed. > > I made a mistake in my last post. There's actually no reason > byte-optimize--dynamic-vars shouldn't contain symbols with position. > That's what it accumulates. It is also meant to be a private variable > in the byte compilation (hence the "--" in its name). > > Why is async-bytecomp copying byte-optimize--dynamic-vars? There seems > to be no reason. You are right, there is no reason for this particular one and also the private ones, however we used in the past to load all byte-* variables for a reason I don't remember, IMO it is not needed anymore to load byte-* vars private or not, so I removed this. > Maybe any variables with "--" in their symbols should be filtered out > of the copying operation. Name space problem, byte-* vars and functions have no fixed prefix (not always). > > > Also, is printing followed by reading really the best way to get a copy > of a Lisp object? There are several Lisp types, possibly most of them, > whose printed representation can't be read; things like buffers, > windows, processes, ..... I think only the really common objects, like > lists, vectors, strings, numbers have readable printed representations. > >> Thierry has removed that variable from the list of handled variables for >> now which circumvents the problem. > > I've had at least two Cc:s to Thierry at > bounce with "address does not exist". Do you know if Thierry has > changed his address, or could it just be Google playing more silly > games? My fault I didn't update my mail address in async source files, will do soon, sorry for this. Thanks. -- Thierry