From unknown Thu Aug 14 20:54:30 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#54433 <54433@debbugs.gnu.org> To: bug#54433 <54433@debbugs.gnu.org> Subject: Status: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Reply-To: bug#54433 <54433@debbugs.gnu.org> Date: Fri, 15 Aug 2025 03:54:30 +0000 retitle 54433 29.0.50; Invalid read syntax: "#<" with async-bytecomp reassign 54433 emacs submitter 54433 Michael Heerdegen severity 54433 normal thanks From debbugs-submit-bounces@debbugs.gnu.org Wed Mar 16 22:55:35 2022 Received: (at submit) by debbugs.gnu.org; 17 Mar 2022 02:55:35 +0000 Received: from localhost ([127.0.0.1]:52669 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nUgIZ-00021L-3h for submit@debbugs.gnu.org; Wed, 16 Mar 2022 22:55:35 -0400 Received: from lists.gnu.org ([209.51.188.17]:55538) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nUgIX-00021C-Gm for submit@debbugs.gnu.org; Wed, 16 Mar 2022 22:55:33 -0400 Received: from eggs.gnu.org ([209.51.188.92]:60816) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nUgIX-0002tc-96 for bug-gnu-emacs@gnu.org; Wed, 16 Mar 2022 22:55:33 -0400 Received: from mout.web.de ([212.227.15.4]:58005) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nUgIV-0001d7-CV for bug-gnu-emacs@gnu.org; Wed, 16 Mar 2022 22:55:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1647485728; bh=pJRiugcCcQtdSYmF6VOOqMt4NahtSbFLh2Zon/i2k8M=; h=X-UI-Sender-Class:From:To:Subject:Date; b=FTbdZAru7JV46CURQJveHSHgEjP9v/rGSHn2nReT0O2o1309r5yA6DwobJfAghHA0 HEdfLDWfgTM2eMPVfHhVAXm3d0FSoWj1u3nHq/Ic3qynGYKecmTT7m3vWeClxuGiwX oUoCaJiZKPTLEw5IYTVDl0UmYGdpXR8dsw4Booe0= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from drachen.dragon ([84.60.174.212]) by smtp.web.de (mrweb005 [213.165.67.108]) with ESMTPSA (Nemesis) id 1N7QUL-1oBmQk3tsb-017U52; Thu, 17 Mar 2022 03:55:27 +0100 From: Michael Heerdegen To: bug-gnu-emacs@gnu.org Subject: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Date: Thu, 17 Mar 2022 03:55:27 +0100 Message-ID: <87a6dpnv8g.fsf@web.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Provags-ID: V03:K1:NszMifdqMEojSggOzhdGYwcANPdExVpDQchTH8tE+1EdaoxxdYj 22N2IjeFA5d/YwCHIXiIzpBfZYT/XklxV29RoGWciaa4yJLotvwtNK5zDIUH30/lhD60+y6 avrjYhQF0Izo1qPu/ZJW7Fw+Nu27nsMhEDCH/kNUenQ7Zw5fBHnqrARF7/DAbVRbCCgju9v z6mOzL1XiMHNeJmaeC5lg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:Fgyq0TYI87c=:Tw6/Od6jo9h1HM2HZshRUw WLqUJdnnr6C4XapCtoZK2rb0KMSQYaFpodugHM5bLPfEqyfTEk33oSHivBCEXJCSb53kuWNKe WGnX9yYGTb6aqUMrBpPhjTKzJ6c3pwk84Ld0bgxDk+hH3bAwUbUXDRkjSBdkWLbSohZtmsoa5 J25JVupczS36ER+D6xUk7rrsnkNkfcljzKpTsyRHley8tS1KgRWiIi+u5/3cgcSv2/YarUyE7 dlZ+XiJFEs6KmQ2e+Zg0s6k/HFDtHYoweagnrxDGMz9zsnF3x0Do27zf8eV9TTLjWhu6kCdcM VBlDvfnfB291tZKz6dOny4B0WLRFfPuMKFEN2hat54YU90xar8SPHrOttn2pgHwwE2Mhkju/5 HDuy3bLc809IcGUIBwwWLvzStHf5oBNOpw7mO34WtVurqNFexLveGpEgZUEjosf05YRzKcBJO WHyX6H3LDM7Xs6txbudihOELsteAq6rB3MZngY+iNFbAdHwYE+fKnWIGhcYcZYFqpwlhdVMOJ /scRXjJpsNFojEv426Z6eIQnIRoK34PPZIt3LJRwqHncO28WXPHKE3XktDI8DRi3oH9ew6Az8 udyTkvu9tKnF1hM4tI33VsrP1GDZSMlcF+/RqyWMh0FphF8C95U9qH4kFzlFYjyB8IyKWozHQ My3Ndao6sSw/1GJQsGA2jHgGYsk2NcMWvq2W9MJyDhzMCnVxvc00PsZTkRDDdPmCT5lzndJYU H+9fAD4NJmByjGZW4njQtIIJ40UWgiSyXaQ7SC0BebhE4yDwirEVO/XMekte9/HUWx0KrHBvG p8UIRDXV9TMorbrf2muZ3UwFHPpuOA4ZvEEt4B0p5iVmpI67SWcmz04AmUXxgLONzdvN7cjnw P10AZ2g3hKcmJx2tv4FxvNA39Lmi79x2Tuc38dE+zGvr/FpXaWfgDs9cpq2zZnypgyliwnVKa gY81+xAnLVAPQR8tx3DDL6A9DFiItEarZrluBVfRdFromqAPixfP2SoJfH03XyRsf0KHGfqi5 TF0BYfrRbTFnTuJpUDSpgrv3sj8hLGRbAxPaA8S2R00lEVDM/zCQYIE08zZDCab8E8URZWAq7 qGMD0td2bWrCO0= Received-SPF: pass client-ip=212.227.15.4; envelope-from=michael_heerdegen@web.de; helo=mout.web.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: 0.2 (/) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.4 (--) 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: "#<" This seems to be related to the recent addition of symbols with positions. 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'. Is that expected? What has to be done? 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' From debbugs-submit-bounces@debbugs.gnu.org Thu Mar 17 07:28:28 2022 Received: (at 54433) by debbugs.gnu.org; 17 Mar 2022 11:28:28 +0000 Received: from localhost ([127.0.0.1]:53219 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nUoIt-0002zT-RY for submit@debbugs.gnu.org; Thu, 17 Mar 2022 07:28:28 -0400 Received: from colin.muc.de ([193.149.48.1]:52544 helo=mail.muc.de) by debbugs.gnu.org with smtp (Exim 4.84_2) (envelope-from ) id 1nUoIr-0002zD-LY for 54433@debbugs.gnu.org; Thu, 17 Mar 2022 07:28:26 -0400 Received: (qmail 893 invoked by uid 3782); 17 Mar 2022 11:28:18 -0000 Received: from acm.muc.de (p4fe15a13.dip0.t-ipconnect.de [79.225.90.19]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Thu, 17 Mar 2022 12:28:18 +0100 Received: (qmail 4577 invoked by uid 1000); 17 Mar 2022 11:28:17 -0000 Date: Thu, 17 Mar 2022 11:28:17 +0000 To: Michael Heerdegen Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Message-ID: References: <87a6dpnv8g.fsf@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87a6dpnv8g.fsf@web.de> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 54433 Cc: 54433@debbugs.gnu.org, acm@muc.de X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) 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). From debbugs-submit-bounces@debbugs.gnu.org Thu Mar 17 19:50:28 2022 Received: (at 54433) by debbugs.gnu.org; 17 Mar 2022 23:50:28 +0000 Received: from localhost ([127.0.0.1]:55666 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nUzsy-0001X5-GL for submit@debbugs.gnu.org; Thu, 17 Mar 2022 19:50:28 -0400 Received: from mout.web.de ([212.227.17.12]:41659) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nUzsw-0001Wp-9k for 54433@debbugs.gnu.org; Thu, 17 Mar 2022 19:50:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1647561018; bh=Gyh1EGQ3guc2+9u8+co+ArNLchcqb2PttTTHjDUWD18=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=PSnzgBurX+lB/k0pTa4zW00eWs0S/o8MO+EmsbuDGDnoPY6B4tOEKpE8J7U/ll51x 7eV1wRcLiTYtDc9XzSS8n3xGv6M8UuZKHVCqzMd+pXcAoySwTr9uMCuYLsQb7Tc+8X kKcUn0nZBQ/8DIiGTCnA1jJL2Fs5OI9Xh28yvCw8= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from drachen.dragon ([84.60.174.212]) by smtp.web.de (mrweb105 [213.165.67.124]) with ESMTPSA (Nemesis) id 1M7usy-1nQ4CG0YAU-005Com; Fri, 18 Mar 2022 00:50:18 +0100 From: Michael Heerdegen To: Alan Mackenzie Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp References: <87a6dpnv8g.fsf@web.de> Date: Fri, 18 Mar 2022 00:50:17 +0100 In-Reply-To: (Alan Mackenzie's message of "Thu, 17 Mar 2022 11:28:17 +0000") Message-ID: <87fsngm952.fsf@web.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Provags-ID: V03:K1:kXJy9/etMv1RYGJ7szvveMRpdSRIo7efglbVllqgxG4FlAxMSRB LuCdW2oOc9j4x1CKXTM/rp0RG2SGfbXMgGFLUJN6BCRyZB8BtXUMII+fFL7Zq06jjgxw4ZT fJWK+evmMdVyOUQoGqYDEG/4WMYdCaQzX4biOa/WLUC9nhbiwP/+JLs6kWD142UVBbWEAdX R702jh4inusHCnj8KTNrA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:o73s0i8t550=:MyNatFZVyi0eOdwLcLNLIg nXMbsjrZlB8TXcIp26E0YliimDtQu4qKFaQS3lbsUV3Ev8e446BJ9srTGM+vBsxzwufMsYZLf tiJrQ3lDENefpl+sf6VgeZJmhTDzu/2DrBcbO7M40v3oyYwzPlYPhKfcuPlynkoGHOmKFibVo GB32vSj2STo1YV645E1xW5CFQYtrFLkpr1A0eXPk4wf8J3t7nLcTfuKOZpEy82qFgSyrOp4iX cYOYmCrwpQNQTqp1+SePdh5hn7PnWC856mB3GPg9NaeXBMdaV6Ow5gHoS6qzDBsKssWujEa7F cWv0HWCk7sIkH5uKos+yA8+XtA0q81g1rcXGX5MT5xbDeiIkV1yVe5SLZsgZYBG3jnoSyZhAb /FZfzK03YLH/Jr3iozfudfyuorTm90svgOI3uWf6UDsHNCrRZR23Lj1SQ1xTHhLWmuFJWEhWb ZRkOKtNzS3siJ7RFvHzCjHfP1s7S7s6P+cqGtpCztcSo3J6JPnXYMkSSSO+Ie6pn3NE7gzx45 uBl7QUTiLpLTCY7nIS3ls42NBE0kf6E1jH4/Uk/rz0n2HDXF4OGpjcmPouj0s+g2OedL/8Rzq O7A+Aj4VthvB1LAG9RfpuR9wrDT9Z/4vN3IM3UJ3ZNxby2vtOv/4rGzS8HTkEd7mw0W8KyIXd NoxAlwzl7vWhwsHz5vlfXl9eNDIr7wNcEHTiXcGaP0hOnsXNOc0Ds3S5YHy3mAbLuI7wxAaI9 tQGH+kAJhr8yjDhqgvovShYrnioQuBn3SMkNdS82EvfOZ5PJC50ZBYYz8jEgKXcTjX1tDyZxr xoOOhsoF3+hlwrhyJ2qfBGGkzdN8BZTnqHRf4+uef6Au4B3bH55KBmUMd9qswqzCnyCaCp067 e0+3SGBX4g+w+lprOaU4ufzjERUrNpbztdi3YxfVT8W8gKXZj+oc+4+NU3ZzfIUHYYQye3Et5 gm6lp8+g00RaBgZLt6k1B+Z96akWanrTIFI1ek410hfK6aJE8DVvhKPPSGi62I0NBiiR1MHBZ cRtKMS9lFdZpzklDDSi8BfaT8/aNMVNAye9M7r4UX7oPG7sjUzIkJgNM+d134UzJVlMd9MGut WfpW75ppyz5+nA= X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 54433 Cc: 54433@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) 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 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. Thierry has removed that variable from the list of handled variables for now which circumvents the problem. Michael. From debbugs-submit-bounces@debbugs.gnu.org Thu Mar 17 20:09:34 2022 Received: (at 54433) by debbugs.gnu.org; 18 Mar 2022 00:09:35 +0000 Received: from localhost ([127.0.0.1]:55680 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nV0BS-0001zP-Ok for submit@debbugs.gnu.org; Thu, 17 Mar 2022 20:09:34 -0400 Received: from mout.web.de ([212.227.17.12]:51573) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nV0BQ-0001z5-Ad for 54433@debbugs.gnu.org; Thu, 17 Mar 2022 20:09:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1647562165; bh=P6uxx5NTl2lflcXniZSUGcVtt0F/FVi5bP9cr5lTOLw=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=Ih4jndUY9HJMkx88PZ0lQ5mN2MlaePc6gnYDGsk7RXotX2vdAxJg5j+F96xtv6jdJ L7gv6S2cROXajG7lRwWEVMfkS/8JlzPf1Gkslila+w6w2IgYMH5vQcHC5rF2akOYKY nCD9pUeY7e1krTTCnOvpQDAA9Mdqpn66e/RNOVeo= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from drachen.dragon ([84.60.174.212]) by smtp.web.de (mrweb106 [213.165.67.124]) with ESMTPSA (Nemesis) id 1MZB07-1nZ6mq1Bon-00VD34; Fri, 18 Mar 2022 01:09:25 +0100 From: Michael Heerdegen To: Alan Mackenzie Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp References: <87a6dpnv8g.fsf@web.de> <87fsngm952.fsf@web.de> Date: Fri, 18 Mar 2022 01:09:24 +0100 In-Reply-To: <87fsngm952.fsf@web.de> (Michael Heerdegen's message of "Fri, 18 Mar 2022 00:50:17 +0100") Message-ID: <87bky4m897.fsf@web.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Provags-ID: V03:K1:SCT7V6fJdMN8wqEZQOCauDep/x9QspI92MKLpttr6TYCK4qq+eX +lUboIrjyjp+6B3gXK5HFCWtxmZNSNfI00PpJTQBvn91NyJhLdSQBDNdggmPC70K5lPnEgb Ak014GlRYu66A/PAt66FJzdHLAuULGPYYXvup1PVEYhq1Dr3gh0q/APHsWxpm9TQVlbyOLb LJuRiSzww/DQRb1s9ppow== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:wOpjEteokzw=:40Qnm/vvJdMjH/6TP0vXpS ORzYLdc4qz7PCBADcs25CFV8s+rwEo8IYTvtJzWeHmMi8S9GphCvy1kMVBJZt5ZNYiqAkGM1U mivmEQO2Fbtwenuk7wjO8ccwz7SDYqb9ZtALtWCtHMTE08uAJxAT93lYJ34Ddg4DqjsVzP84T M86M3V58QNcfWKZyZNLtCNCWCftemAj12LiCu05YvjVjIQeh14h3/uGi1Kkip76Rqaj0HnqBn Z4wpoc7jn2tQBpeJCRuv4toh4b1FJ/k2n8JW2Ci0tqb5HoHPrvlEbTATjFmhAtEWii2OcfYq0 VM8ySEumc/KxO3qa8GHkFu5AZmDBFnhjhVP4mLFpJLoPM1n0E7eEuxa5KwC7N0dYaAJF9iCra 0lnGo+S1RxGUQNz8HuGUQ9RU8iGd8JOoZdEELC8WMb4UZPGk11Ks+XKZ+qDpRracB2xi/gvvZ Gzibsw98vkYmqN5ye6WSdjLn6PhVyaZYEiKNbx7G7DPiYR/IUtHISAZzfp9Fgce68baHN4x+Z jgscEbb2PGm6sVgQUOROA6tvjm0UUr4jEnAjiwns876n1WftW+C4G0ls0u7p/A83pLdxNwl2Y jnobklVNJ7SlNcdt1ejBhmIM9MuFjWNE0xAwIu09c2ZDRz1XIdSMmCC0iGi9QA9N4qrcnVwxd /zY8iBUfAD6KmHPhC/JqkD0DaHfoxEYhPW06gyKuJsDQJioc7Y2KGZtQckWYZiIfKLJZwVDgc T4dMZCWqmZVG7Q80sUlCzHkQvvoybZheRPUJyw6uJmC2U3oKAn1jPei18gDjDr+EJD2eGZ+9N tQdnwQ8cGsGEyrRdWudCNZXuJu0aAAg8K3fplOpVKc8fTvghyXFsdxqjWpGoEM8GnHhQYViUM qdrccn/7DG04h9Z+xbFeRvdCRUBdm3dYQIp5Fm+7WXNs96mDmt5Ll1ens2toAP0bcJRHITiui Qu26qjeUjyIi8lQpwADX0HeGB2GFiAmeRldXX8rwpFJxApUFl7K/fQOyOZpEbWvafyQlLMDEz PDNCz2+5JWJdHjbh882xhyUjFFWsni/9hMWmVDHcN3FUvZM5YrVUj53u2Ydd9H9pDinJ+dLnM 1x6QG/0g/f858Q= X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 54433 Cc: 54433@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Michael Heerdegen 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 -> > (# #) ... 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. From debbugs-submit-bounces@debbugs.gnu.org Fri Mar 18 07:58:43 2022 Received: (at 54433) by debbugs.gnu.org; 18 Mar 2022 11:58:43 +0000 Received: from localhost ([127.0.0.1]:56464 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nVBFj-00006U-By for submit@debbugs.gnu.org; Fri, 18 Mar 2022 07:58:43 -0400 Received: from colin.muc.de ([193.149.48.1]:37168 helo=mail.muc.de) by debbugs.gnu.org with smtp (Exim 4.84_2) (envelope-from ) id 1nVBFh-00006D-8M for 54433@debbugs.gnu.org; Fri, 18 Mar 2022 07:58:42 -0400 Received: (qmail 32330 invoked by uid 3782); 18 Mar 2022 11:58:34 -0000 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 12:58:34 +0100 Received: (qmail 12242 invoked by uid 1000); 18 Mar 2022 11:58:34 -0000 Date: Fri, 18 Mar 2022 11:58:34 +0000 To: Michael Heerdegen Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Message-ID: References: <87a6dpnv8g.fsf@web.de> <87fsngm952.fsf@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87fsngm952.fsf@web.de> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 54433 Cc: 54433@debbugs.gnu.org, acm@muc.de X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) 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. Maybe any variables with "--" in their symbols should be filtered out of the copying operation. 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? > Michael. -- Alan Mackenzie (Nuremberg, Germany). From debbugs-submit-bounces@debbugs.gnu.org Fri Mar 18 09:37:54 2022 Received: (at 54433) by debbugs.gnu.org; 18 Mar 2022 13:37:54 +0000 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 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 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== 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) From: Thierry Volpiatto To: Alan Mackenzie Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp References: <87a6dpnv8g.fsf@web.de> <87fsngm952.fsf@web.de> 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/h03K0rWhUFLDocpnWwI7mPq33oR9N u2XMNtUQeWhhZHj8dvpMazWIR/c4iPnQiIobETISNlKIVo7DZSl67btoBrZygVYobgHpAYLBpHtH pXUcfM+Jrl8ytLouZ2XYeqzezr1qUDXhPk6mXtEVLJsK4FSS4wT5hPpRozuIwj6sE8OGJIp5uUhm SYm9mjRNJBEgmGUNxMQ/wbcA3NEWxBeIZbRvxMgHG47GJ0TJM4xLpGC8BHUZvuIw05gAtgoA3BGh 5GXbLWy4fi8ozJA/kCkP43d3zh4wTOfQterVTf90bbw6NiNcmXdKH7E/yO1or06bleza39PJsshX 8EETESzVIifk2yDnc0/CQ+FrLY9IwOOszkMouFXmiwN1xMkjuQGNBF8ylcIBDADnIDHEkmk4lUwT lOhwb2yjUfmGPnpH3MCCHkjM9H/P1gTHxFWtwFVPcNMCwXWvKSBTF2dZXKERD0yzG06zT53ZMN7E IIeuY6m4R8IcMvpohciisWxbFoB4ZY117tVSeqjo946itgbpdeESKl9a8dpn7ytZMyYxPdojlQAq xeAJ8444raESh1oTKXb64hlk4l2pSRlrLgjpJBo8asAfZndaxIUKhw68tV8sqeZh9P6cGtHbUELK VJqefNV7V7jF5wf3xvRG6Ces3kSKXalLfs+vrVaoOjQeWrc0AtwFWHmt9JLfKrqF+Q2Q7jUidboW mazQM56ESJFPpPHmWq8k6DHspsFHOforLouTHJL1556IPne7IV2BGfWc0+xLxalZ8F5F+vnPF/Ok rC1CD5iCKTjXKa2iZbcYdYQAiL6P8Ac8CgN6EkhpbxRtzrEgChuNGevdi/G/GHG4Zqrh6YFwIa/N Hq2aVaFq5C1yNTMJd1FRjRzs5JPPlJKpYDnNx+MSp7UAEQEAAYkBvAQYAQoAJhYhBCPbcH0Te695 4oP8cA7FbRQdFu+TBQJfMpXCAhsMBQkDwmcAAAoJEA7FbRQdFu+TXsEL/3nCs8oDLBSTPXylenWK CYLdfZSg8jmwgRKihktU1ZLf8kL/LtEhxdKc9nYQO0gTYdPQ+HEdFbm+gFZ4AxuCtd5zM+MP5Sej pfr93QbLwYCiqsudKa+T7wosBBNFnh8ZQkbnsF6iPIeESCJM0Vhjh1lQ+z1qVkdf/yazwmXspOUh 3kx8dzJQ1F3t6Dj/zHpdNE11bT6wFwTPBFvFeH0yCwDpvVcLbH0xf/0V/RhwkQ4jjae0Cqn8domz RpGODjXkAzoRqpRL9/DvIKTQ/uJQqzu6qvi04foFCmtWTSahJiLtbgHSDNj1HHOivtgeTgtVdAEk ZAqAXJfmaM8KkEi8Rqcbz3AzkjNWjQNkel0xjB3wkewds1iGcvo2/etWOXcvFiLUpy7YnLMZ4J6d jNpwSwDzxvJVy0OvB9SgVF0hX5DdbKTRBSZpGYQgoVdPelGnqs6uq8fa1Ker587E6O6haTIX779d pd5UIX75/XbtumwE0L+IvMpekoM9zH8pCowu4g== Date: Fri, 18 Mar 2022 13:37:43 +0000 In-Reply-To: (Alan Mackenzie's message of "Fri, 18 Mar 2022 11:58:34 +0000") Message-ID: <87sfrfpejc.fsf@posteo.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 54433 Cc: Michael Heerdegen , 54433@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) 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 From debbugs-submit-bounces@debbugs.gnu.org Fri Mar 18 17:28:42 2022 Received: (at 54433) by debbugs.gnu.org; 18 Mar 2022 21:28:42 +0000 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 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 Received: (qmail 40174 invoked by uid 3782); 18 Mar 2022 21:28:33 -0000 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 Received: (qmail 7483 invoked by uid 1000); 18 Mar 2022 21:28:32 -0000 Date: Fri, 18 Mar 2022 21:28:32 +0000 To: Thierry Volpiatto Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp 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 Content-Disposition: inline In-Reply-To: <87sfrfpejc.fsf@posteo.net> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 54433 Cc: Michael Heerdegen , 54433@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) 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). From debbugs-submit-bounces@debbugs.gnu.org Sat Mar 19 02:24:56 2022 Received: (at 54433) by debbugs.gnu.org; 19 Mar 2022 06:24:56 +0000 Received: from localhost ([127.0.0.1]:58886 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nVSWG-0004pi-Bt for submit@debbugs.gnu.org; Sat, 19 Mar 2022 02:24:56 -0400 Received: from mout02.posteo.de ([185.67.36.66]:35581) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nVSWE-0004pR-9E for 54433@debbugs.gnu.org; Sat, 19 Mar 2022 02:24:55 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 385B0240103 for <54433@debbugs.gnu.org>; Sat, 19 Mar 2022 07:24:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1647671088; bh=Lrfto5sgMjQlBcBxTi6SpjoNoGugSVFdvmLpN2wFWe0=; h=From:To:Cc:Subject:Date:Autocrypt:From; b=PvkQk+THwO/zdaU7FRAXjqgYrjQlGggwCQ0Mx/DWqzdb30lkOfyhLBB9P9WfPoqLr y+Un3PaDTVfgj8B2lrrE/SNZOxOkSOMIsea3cznbziLVZCQVY/ljUrQGBPZi22+s2J aZ3zJj8DB30HZA3uRscMpN+/2tpjy+q/oXLNtLFb0KZWdHrFGjFLaeohLGBC8GGuJT r3ROVzJqIL05ILR0WzNMEMihe+VHMQJfqmSKxwy08uwGzwvyZFa4U0AQ40bYwLpEa/ qm+RUNJoxDS8t2UToZzCmT9sm8EiB5AjPhDkJWOtkh2B97lQcnDkuOiMGhWy/na2W4 9YGmVHo+VTrww== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4KL9pQ3BPRz6tm6; Sat, 19 Mar 2022 07:24:46 +0100 (CET) References: <87a6dpnv8g.fsf@web.de> <87fsngm952.fsf@web.de> <87sfrfpejc.fsf@posteo.net> From: Thierry Volpiatto To: Alan Mackenzie Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp Date: Sat, 19 Mar 2022 06:17:36 +0000 In-reply-to: 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/h03K0rWhUFLDocpnWwI7mPq33oR9N u2XMNtUQeWhhZHj8dvpMazWIR/c4iPnQiIobETISNlKIVo7DZSl67btoBrZygVYobgHpAYLBpHtH pXUcfM+Jrl8ytLouZ2XYeqzezr1qUDXhPk6mXtEVLJsK4FSS4wT5hPpRozuIwj6sE8OGJIp5uUhm SYm9mjRNJBEgmGUNxMQ/wbcA3NEWxBeIZbRvxMgHG47GJ0TJM4xLpGC8BHUZvuIw05gAtgoA3BGh 5GXbLWy4fi8ozJA/kCkP43d3zh4wTOfQterVTf90bbw6NiNcmXdKH7E/yO1or06bleza39PJsshX 8EETESzVIifk2yDnc0/CQ+FrLY9IwOOszkMouFXmiwN1xMkjuQGNBF8ylcIBDADnIDHEkmk4lUwT lOhwb2yjUfmGPnpH3MCCHkjM9H/P1gTHxFWtwFVPcNMCwXWvKSBTF2dZXKERD0yzG06zT53ZMN7E IIeuY6m4R8IcMvpohciisWxbFoB4ZY117tVSeqjo946itgbpdeESKl9a8dpn7ytZMyYxPdojlQAq xeAJ8444raESh1oTKXb64hlk4l2pSRlrLgjpJBo8asAfZndaxIUKhw68tV8sqeZh9P6cGtHbUELK VJqefNV7V7jF5wf3xvRG6Ces3kSKXalLfs+vrVaoOjQeWrc0AtwFWHmt9JLfKrqF+Q2Q7jUidboW mazQM56ESJFPpPHmWq8k6DHspsFHOforLouTHJL1556IPne7IV2BGfWc0+xLxalZ8F5F+vnPF/Ok rC1CD5iCKTjXKa2iZbcYdYQAiL6P8Ac8CgN6EkhpbxRtzrEgChuNGevdi/G/GHG4Zqrh6YFwIa/N Hq2aVaFq5C1yNTMJd1FRjRzs5JPPlJKpYDnNx+MSp7UAEQEAAYkBvAQYAQoAJhYhBCPbcH0Te695 4oP8cA7FbRQdFu+TBQJfMpXCAhsMBQkDwmcAAAoJEA7FbRQdFu+TXsEL/3nCs8oDLBSTPXylenWK CYLdfZSg8jmwgRKihktU1ZLf8kL/LtEhxdKc9nYQO0gTYdPQ+HEdFbm+gFZ4AxuCtd5zM+MP5Sej pfr93QbLwYCiqsudKa+T7wosBBNFnh8ZQkbnsF6iPIeESCJM0Vhjh1lQ+z1qVkdf/yazwmXspOUh 3kx8dzJQ1F3t6Dj/zHpdNE11bT6wFwTPBFvFeH0yCwDpvVcLbH0xf/0V/RhwkQ4jjae0Cqn8domz RpGODjXkAzoRqpRL9/DvIKTQ/uJQqzu6qvi04foFCmtWTSahJiLtbgHSDNj1HHOivtgeTgtVdAEk ZAqAXJfmaM8KkEi8Rqcbz3AzkjNWjQNkel0xjB3wkewds1iGcvo2/etWOXcvFiLUpy7YnLMZ4J6d jNpwSwDzxvJVy0OvB9SgVF0hX5DdbKTRBSZpGYQgoVdPelGnqs6uq8fa1Ker587E6O6haTIX779d pd5UIX75/XbtumwE0L+IvMpekoM9zH8pCowu4g== Message-ID: <87pmmi5uj9.fsf@posteo.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 54433 Cc: Michael Heerdegen , 54433@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hello Alan, Alan Mackenzie 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. >> > 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). >=20=20 > OK. I think you're saying that there are other variables with "--" that > you _do_ need to copy. No, not anymore. Wanted to say that if needed it is harder to catch foo--, foo-this--, foo-else-this-- etc... instead of just foo--. > Well, we're back in communication again. :-) I've heard good things > about posteo. Yes, works great :-) Thanks. =2D-=20 Thierry --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHHBAEBCgAxFiEEI9twfRN7r3nig/xwDsVtFB0W75MFAmI1dyoTHHRoaWV2b2xA cG9zdGVvLm5ldAAKCRAOxW0UHRbvkz+hC/9Rzwxb5kSLRtpCb+OkF8W8HWCpZCye +0obQuYedHDet1NjJTUiJcuc+aRm6xlKouQdrSFXi5fBzGOgD6g7iDdMWGYtqZqY CTP/1jejOGro5qn1zRbaK0R+I7w04uXi8jhA73dqiAAFSTbMzAtyoEEVn5nNlwFg FeaxLp7TrtDjxxXhqLlb/Mz8Vb411Tda90UGCvlZbFukCU9cM0lGzSOultjhpHoE tUKsNWCLFw+sNOhtNRcjRW1s4jFNY/xsE5TGJP0F4rFjmEIo7ibaBpKw7F8bESrR O54b+WIHJH+MleogE+jaM0R3v2OMkkZtxGtjQE5UrVot4eSRfDzzhCjFTsD6kFpJ 6PtpGioPZ6NUyuLV4MhjH6JuSTPPnTuRuXDAu1VNxKUOjXznFnImOKlJW3vLldIx Qpe8Fcx9h705HfuLoyqA7CmtdZHHaHTo+wuwrf3TdTF5FWa9h8D1+5ilr7ZF2zjG RN/yR6yO9CZ82yp0+ZhFNrXXVJ3GQ4pqDhI= =Cn59 -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Wed Mar 23 21:38:29 2022 Received: (at 54433-done) by debbugs.gnu.org; 24 Mar 2022 01:38:30 +0000 Received: from localhost ([127.0.0.1]:46443 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nXCQn-0003gT-MD for submit@debbugs.gnu.org; Wed, 23 Mar 2022 21:38:29 -0400 Received: from mout.web.de ([217.72.192.78]:33689) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nXCQl-0003g9-HU for 54433-done@debbugs.gnu.org; Wed, 23 Mar 2022 21:38:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1648085895; bh=/fUYC8oAZsXMS47gFHl+ug56pG7/ZJdXIhrmTq03/jQ=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=ERioRxHeVRVADbu0PntOJtgJoRSCgnh7bcDF4tT2Hx5P0MMhk0Ka7PLZZk2tYhrFQ 8RGCS7waDw0EAToBeoIM0GaLtjXDXwm5TbqIu+gPDbgfPNFQPfBlyQkIODqyi4yINw 97WDVp6BM45tEIkcbBoCaYru8/SYjx2I+2aDNjyM= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from drachen.dragon ([84.60.174.212]) by smtp.web.de (mrweb106 [213.165.67.124]) with ESMTPSA (Nemesis) id 1MK56y-1nn4cT16Pm-00LW6C; Thu, 24 Mar 2022 02:38:15 +0100 From: Michael Heerdegen To: Thierry Volpiatto Subject: Re: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp References: <87a6dpnv8g.fsf@web.de> <87fsngm952.fsf@web.de> <87sfrfpejc.fsf@posteo.net> <87pmmi5uj9.fsf@posteo.net> Date: Thu, 24 Mar 2022 02:38:14 +0100 In-Reply-To: <87pmmi5uj9.fsf@posteo.net> (Thierry Volpiatto's message of "Sat, 19 Mar 2022 06:17:36 +0000") Message-ID: <87fsn8ku49.fsf@web.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Provags-ID: V03:K1:zGXwDV9fujmvsYEqDHJEVYIN0iHtBcXHKvLsjpbVMfnOTbDwTRr JMp+uI1/97Dn7Ay+VZAJDaAMdzAH0QOifbCoH0rl2r2cO7Z6hOCQVz+x90/4HyM325nP8rQ ieQbLw5DjMCCSHnxe7CXyxa/TOJAJwEfZ0J38+GEXJQOR8+6cDvF5vEIswyNe/1/kO6Rk7f MieuhI0vFngoDyMX4RvSA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:K0rwbuV92vY=:cvfqnqgSJPT2DOi7n4vEwj 9dPmuq9caqJu3gigJ6JppxRFxm1pKRQsxRaEYfpTCY/5DmtMeHPHSePrlG8wcnMvRTOdLdqoZ 0ytnK0SI/OK9vlUScdwDOE13Fa5qNjrX3CS2SWl+TLlH7jDHfiEcOhmB76yvMFbiAhR4YN/ZZ ecYjxPN63f72kjYt4Gfkg8kIKWGY7RupvmaZuT+jjFBQKd6bXp3NifBHYuIYH8T6aACeTs0eR QsrtPPD54Q/oEwQu8utw3l43H1wwfiER/oIJ87GqEPj2N9GOA3v6qE3mYnwIbGvJd0R/DtQ83 rn8qDVbwrWUON9nY8esJ78A149Wq0XZ9iIql7/fVWmHbuycBlE5TGL+vzlFx9qm31xtpL1Gn2 bHOIJyKyztV3usTgiqRkfp3GUc7bgOVe3HCc25AOf/7iIXzHXslOM0TH2LBstWyrK7rxeYMFI j81tr4JEAFzOi/eUIuixw38ZiSP/OGDTzwARrEOYoNHtbDeEQjX7rrkG2njVEktQ28aPY3XLP 4wVZYoRfn/zBLV7rUYZo1TetM+UNbnHAkJuvwW3xJGjzdsCuMj3cKL6Xk/PwjRTtD3iFSXUIJ GEdzCsLU3/JS0DvME4ZOQZ5dRCMwVMEcINYna7iXlx71wsDXI0uYLescUjKQEWlSUJPqdILq2 idQB8mWrO1EuSmCoPUXbXWbgOWdqXzrsWSe8gmkHi3jB0in6oCbtWWKAqjQLszbX8dXe+iEbC q95TYWw83uHzOZYzNM/TAyH3LezWwXo1zaY5psy2Vazunc8UgqquQCH09OX5J4BC5aCcook/E 2BRfJpQVHS9tYAq33gJPPVnu1Kzg5Wej8mjhmhtgH9qIylf5HVKf+PlaomExRGDGfst1fnROI 5JO48AW4nZXxnLypJ6XxyWqYKqCFFh1i32LY3iS5LpzJauWM+fbXnbPPxYz5hIyCf26QGoh9c sfaZ3aW9YffTozg8KgdColuUR+Cj37jUO57foqURN5hIXJgebonDh0qHN5po2CCezN6PfCBVz +Em+ESvJKz6CFl5wocftnR1u4hzN9NVPYS1T/Ct05dZov0eHsddkd8b6HZS91Ov5BD1Ydqj59 POzatS8OGTlDN0= X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 54433-done Cc: 54433-done@debbugs.gnu.org, Alan Mackenzie X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Thierry Volpiatto 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. From unknown Thu Aug 14 20:54:30 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Thu, 21 Apr 2022 11:24:04 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator