From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.bugs Subject: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Date: Fri, 18 Mar 2022 21:28:32 +0000 Message-ID: References: <87a6dpnv8g.fsf@web.de> <87fsngm952.fsf@web.de> <87sfrfpejc.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10493"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Michael Heerdegen , 54433@debbugs.gnu.org To: Thierry Volpiatto Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 18 22:29:20 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 1nVK9v-0002Xt-Tl for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 18 Mar 2022 22:29:19 +0100 Original-Received: from localhost ([::1]:51344 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nVK9u-0002yW-Uv for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 18 Mar 2022 17:29:18 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:38430) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nVK9e-0002wp-TQ for bug-gnu-emacs@gnu.org; Fri, 18 Mar 2022 17:29:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36397) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nVK9e-0005SU-Ji for bug-gnu-emacs@gnu.org; Fri, 18 Mar 2022 17:29:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nVK9e-0003uB-By for bug-gnu-emacs@gnu.org; Fri, 18 Mar 2022 17:29:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Alan Mackenzie Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 18 Mar 2022 21:29:02 +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.164763892214981 (code B ref 54433); Fri, 18 Mar 2022 21:29:02 +0000 Original-Received: (at 54433) by debbugs.gnu.org; 18 Mar 2022 21:28:42 +0000 Original-Received: from localhost ([127.0.0.1]:58527 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nVK9K-0003tZ-I5 for submit@debbugs.gnu.org; Fri, 18 Mar 2022 17:28:42 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:52950 helo=mail.muc.de) by debbugs.gnu.org with smtp (Exim 4.84_2) (envelope-from ) id 1nVK9I-0003tI-Ev for 54433@debbugs.gnu.org; Fri, 18 Mar 2022 17:28:41 -0400 Original-Received: (qmail 40174 invoked by uid 3782); 18 Mar 2022 21:28:33 -0000 Original-Received: from acm.muc.de (p4fe15cab.dip0.t-ipconnect.de [79.225.92.171]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Fri, 18 Mar 2022 22:28:32 +0100 Original-Received: (qmail 7483 invoked by uid 1000); 18 Mar 2022 21:28:32 -0000 Content-Disposition: inline In-Reply-To: <87sfrfpejc.fsf@posteo.net> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de 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:228572 Archived-At: Hello, Thierry. On Fri, Mar 18, 2022 at 13:37:43 +0000, Thierry Volpiatto wrote: > 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. 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?). > > 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). OK. I think you're saying that there are other variables with "--" that you _do_ need to copy. > > 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. Well, we're back in communication again. :-) I've heard good things about posteo. > Thanks. > -- > Thierry -- Alan Mackenzie (Nuremberg, Germany).