bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Hi,

When I try to install packages from the Package Menu or the command of
package-install since about two weeks ago, it reports the error:
```
error in process sentinel: async-when-done: Invalid read syntax: "#<"
error in process sentinel: Invalid read syntax: "#<"
```
And it seems not preventing the installation process but stops the emacs
to compile the el files to elc.

FYI. I failed to find out what makes it. It looks like the local variable in
the autoloads file generated by the package process. It add
`;; coding: utf-8-emacs-unix`, however, in windows, the file is probablly
in a coding of utf-8-emacs-dos. When I try to open the autoload file,
Emacs can't regonize the major mode which assumes to be `emacs-lisp-mode`.
Unless I change the `;; coding: utf-8-emacs-unix` to
`;; coding: utf-8-emacs`, it can be open in the `emacs-lisp-mode`.



Best Regards,
Shuguang Sun

In GNU Emacs 29.0.50 (build 1, x86_64-w64-mingw32)
 of 2022-01-31 built on YJ190169-SSG
Repository revision: 04f9c3b8df6afaf1e9de9f2a4478f63fd959bf09
Repository branch: master
Windowing system distributor 'Microsoft Corp.', version 10.0.19044
System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.1466)

Configured using:
 'configure --without-pop --with-native-image-api
 --with-native-compilation --without-compress-install
 '--program-transform-name=s/^ctags$/ctags.emacs/''

Configured features:
ACL DBUS GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES
NATIVE_COMP NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND SQLITE3 THREADS TIFF
TOOLKIT_SCROLL_BARS WEBP XPM ZLIB

Important settings:
  value of $LANG: CHS
  locale-coding-system: cp936

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Eli Zaretskii]

> Date: Tue, 01 Feb 2022 13:32:11 +0800
> From:  Shuguang Sun via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> When I try to install packages from the Package Menu or the command of
> package-install since about two weeks ago, it reports the error:
> ```
> error in process sentinel: async-when-done: Invalid read syntax: "#<"
> error in process sentinel: Invalid read syntax: "#<"
> ```
> And it seems not preventing the installation process but stops the emacs
> to compile the el files to elc.
> 
> FYI. I failed to find out what makes it. It looks like the local variable in
> the autoloads file generated by the package process. It add
> `;; coding: utf-8-emacs-unix`, however, in windows, the file is probablly
> in a coding of utf-8-emacs-dos. When I try to open the autoload file,
> Emacs can't regonize the major mode which assumes to be `emacs-lisp-mode`.
> Unless I change the `;; coding: utf-8-emacs-unix` to
> `;; coding: utf-8-emacs`, it can be open in the `emacs-lisp-mode`.

Stefan, any thoughts?

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Arash Esbati]

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Tue, 01 Feb 2022 13:32:11 +0800
>> From:  Shuguang Sun via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> FYI. I failed to find out what makes it. It looks like the local variable in
>> the autoloads file generated by the package process. It add
>> `;; coding: utf-8-emacs-unix`, however, in windows, the file is probablly
>> in a coding of utf-8-emacs-dos. When I try to open the autoload file,
>> Emacs can't regonize the major mode which assumes to be `emacs-lisp-mode`.
>> Unless I change the `;; coding: utf-8-emacs-unix` to
>> `;; coding: utf-8-emacs`, it can be open in the `emacs-lisp-mode`.
>
> Stefan, any thoughts?

The part above was reported in 53529 and was fixed with commit
35cd9197fc.  I suggest to update Emacs and re-install the package(s) in
question.  The error reported in 53529 was different.

Best, Arash

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Alan Mackenzie]

Hello, Shuguang.

On Tue, Feb 01, 2022 at 13:32:11 +0800, Shuguang Sun wrote:
> Hi,

> When I try to install packages from the Package Menu or the command of
> package-install since about two weeks ago, it reports the error:
> ```
> error in process sentinel: async-when-done: Invalid read syntax: "#<"
> error in process sentinel: Invalid read syntax: "#<"
> ```
> And it seems not preventing the installation process but stops the emacs
> to compile the el files to elc.

"#<" looks like the start of a symbol with position, something like
"#<symbol foo at 666>" which is being returned by the reader recently
when invoked from the byte compiler.

The new mechanism for compilation warning positions was merged into the
Emacs master on Saturday 2022-01-22, which matches up pretty well with
your "since about two weeks ago, ...".

> FYI. I failed to find out what makes it. It looks like the local variable in
> the autoloads file generated by the package process. It add
> `;; coding: utf-8-emacs-unix`, however, in windows, the file is probablly
> in a coding of utf-8-emacs-dos. When I try to open the autoload file,
> Emacs can't regonize the major mode which assumes to be `emacs-lisp-mode`.
> Unless I change the `;; coding: utf-8-emacs-unix` to
> `;; coding: utf-8-emacs`, it can be open in the `emacs-lisp-mode`.



> Best Regards,
> Shuguang Sun

> In GNU Emacs 29.0.50 (build 1, x86_64-w64-mingw32)
>  of 2022-01-31 built on YJ190169-SSG
> Repository revision: 04f9c3b8df6afaf1e9de9f2a4478f63fd959bf09
> Repository branch: master
> Windowing system distributor 'Microsoft Corp.', version 10.0.19044
> System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.1466)

> Configured using:
>  'configure --without-pop --with-native-image-api
>  --with-native-compilation --without-compress-install
>  '--program-transform-name=s/^ctags$/ctags.emacs/''

> Configured features:
> ACL DBUS GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES
> NATIVE_COMP NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND SQLITE3 THREADS TIFF
> TOOLKIT_SCROLL_BARS WEBP XPM ZLIB

> Important settings:
>   value of $LANG: CHS
>   locale-coding-system: cp936

-- 
Alan Mackenzie (Nuremberg, Germany).

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Eli Zaretskii [2022-02-01 17:00:34] wrote:
>> Date: Tue, 01 Feb 2022 13:32:11 +0800
>> From:  Shuguang Sun via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> When I try to install packages from the Package Menu or the command of
>> package-install since about two weeks ago, it reports the error:
>> ```
>> error in process sentinel: async-when-done: Invalid read syntax: "#<"
>> error in process sentinel: Invalid read syntax: "#<"
>> ```
> Stefan, any thoughts?

IIUC the above error involves some part of the `async` package.
Could you give a bit more information about how you hooked `async` with
`package`?


        Stefan

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors]

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

Thank you Stefan and Alan in another email.

With the hint, I find out the `async-bytecomp-package-mode` is turn on
by the package `helm-core`. So it is a bug of `async-bytecomp` maybe,
and I will report it the package author.

Sorry for the misleading information in the orignial email.



发自我的iPhone


------------------ Original --------------
Date: Wed,Feb 2,2022 11:32 AM


Eli Zaretskii [2022-02-01 17:00:34] wrote:
>> Date: Tue, 01 Feb 2022 13:32:11 +0800
>> From:  Shuguang Sun via "Bug reports for GNU Emacs,
&gt;&gt;&nbsp; the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org&gt;
&gt;&gt; When I try to install packages from the Package Menu or the command of
&gt;&gt; package-install since about two weeks ago, it reports the error:
&gt;&gt; ```
&gt;&gt; error in process sentinel: async-when-done: Invalid read syntax: "#<"
&gt;&gt; error in process sentinel: Invalid read syntax: "#<"
&gt;&gt; ```
&gt; Stefan, any thoughts?

IIUC the above error involves some part of the `async` package.
Could you give a bit more information about how you hooked `async` with
`package`?


&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stefan

[-- Attachment #2: Type: text/html, Size: 2697 bytes --]

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Alan Mackenzie]

Hello again, Shuguang.

On Thu, Feb 03, 2022 at 10:55:02 +0800, Shuguang Sun wrote:
> Thank you Stefan and Alan in another email.

> With the hint, I find out the `async-bytecomp-package-mode` is turn on
> by the package `helm-core`. So it is a bug of `async-bytecomp` maybe,
> and I will report it the package author.

> Sorry for the misleading information in the orignial email.

A hypothesis for what is happening is that a symbol with position,
looking like:

    #<symbol foo at 666>

, has somehow got into a .elc file.  The loader (contained within the
file .../src/lread.c) chokes when it encounters such a symbol.

If you have an idea which .elc file might be causing the trouble, could
I suggest you visit this file within Emacs.  There is a mode for .elc
files.  :-).  Then search the buffer for the string "#<symbol".  Or even
just for the "#<" which the loader might have reported.

> 发自我的iPhone


> ------------------ Original --------------
> Date: Wed,Feb 2,2022 11:32 AM


> Eli Zaretskii [2022-02-01 17:00:34] wrote:
> &gt;&gt; Date: Tue, 01 Feb 2022 13:32:11 +0800
> &gt;&gt; From:&nbsp; Shuguang Sun via "Bug reports for GNU Emacs,
> &gt;&gt;&nbsp; the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org&gt;
> &gt;&gt; When I try to install packages from the Package Menu or the command of
> &gt;&gt; package-install since about two weeks ago, it reports the error:
> &gt;&gt; ```
> &gt;&gt; error in process sentinel: async-when-done: Invalid read syntax: "#<"
> &gt;&gt; error in process sentinel: Invalid read syntax: "#<"
> &gt;&gt; ```
> &gt; Stefan, any thoughts?

> IIUC the above error involves some part of the `async` package.
> Could you give a bit more information about how you hooked `async` with
> `package`?


> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stefan

-- 
Alan Mackenzie (Nuremberg, Germany).

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Alan Mackenzie <acm@muc.de> writes:

> Hello again, Shuguang.
>
> On Thu, Feb 03, 2022 at 10:55:02 +0800, Shuguang Sun wrote:
>> Thank you Stefan and Alan in another email.
>
>> With the hint, I find out the `async-bytecomp-package-mode` is turn on
>> by the package `helm-core`. So it is a bug of `async-bytecomp` maybe,
>> and I will report it the package author.
>
>> Sorry for the misleading information in the orignial email.
>
> A hypothesis for what is happening is that a symbol with position,
> looking like:
>
>     #<symbol foo at 666>
>
> , has somehow got into a .elc file.  The loader (contained within the
> file .../src/lread.c) chokes when it encounters such a symbol.
>
> If you have an idea which .elc file might be causing the trouble, could
> I suggest you visit this file within Emacs.  There is a mode for .elc
> files.  :-).  Then search the buffer for the string "#<symbol".  Or even
> just for the "#<" which the loader might have reported.

No "#<" in the elc.

A reproducible example is:
- Install package `async` which includes `async-bytecomp`
- M-x list-package
- M-x async-bytecomp-package-mode (make sure `async-bytecomp-package-mode` is enabled)
- M-x package-reinstall  <= `magit`

>
>
>
>> ------------------ Original --------------
>> Date: Wed,Feb 2,2022 11:32 AM
>
>
>> Eli Zaretskii [2022-02-01 17:00:34] wrote:
>> &gt;&gt; Date: Tue, 01 Feb 2022 13:32:11 +0800
>> &gt;&gt; From:&nbsp; Shuguang Sun via "Bug reports for GNU Emacs,
>> &gt;&gt;&nbsp; the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org&gt;
>> &gt;&gt; When I try to install packages from the Package Menu or the command of
>> &gt;&gt; package-install since about two weeks ago, it reports the error:
>> &gt;&gt; ```
>> &gt;&gt; error in process sentinel: async-when-done: Invalid read syntax: "#<"
>> &gt;&gt; error in process sentinel: Invalid read syntax: "#<"
>> &gt;&gt; ```
>> &gt; Stefan, any thoughts?
>
>> IIUC the above error involves some part of the `async` package.
>> Could you give a bit more information about how you hooked `async` with
>> `package`?
>
>
>> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stefan

-- 
Best Regards
Shuguang Sun

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Michael Heerdegen]

Shuguang Sun via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:

> No "#<" in the elc.
>
> A reproducible example is:
> - Install package `async` which includes `async-bytecomp`
> - M-x list-package
> - M-x async-bytecomp-package-mode (make sure
> `async-bytecomp-package-mode` is enabled)
> - M-x package-reinstall  <= `magit`

Maybe it appears in the communication with the other Emacs instance?

Michael.

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Alan Mackenzie <acm@muc.de> writes:

> Hello, Shuguang.
>
> On Tue, Feb 01, 2022 at 13:32:11 +0800, Shuguang Sun wrote:
>> Hi,
>
>> When I try to install packages from the Package Menu or the command of
>> package-install since about two weeks ago, it reports the error:
>> ```
>> error in process sentinel: async-when-done: Invalid read syntax: "#<"
>> error in process sentinel: Invalid read syntax: "#<"
>> ```
>> And it seems not preventing the installation process but stops the emacs
>> to compile the el files to elc.
>
> "#<" looks like the start of a symbol with position, something like
> "#<symbol foo at 666>" which is being returned by the reader recently
> when invoked from the byte compiler.
>

The issue has be fixed from the package (async) side.
https://github.com/jwiegley/emacs-async/issues/153#event-6295734933



> The new mechanism for compilation warning positions was merged into the
> Emacs master on Saturday 2022-01-22, which matches up pretty well with
> your "since about two weeks ago, ...".
>
>> FYI. I failed to find out what makes it. It looks like the local variable in
>> the autoloads file generated by the package process. It add
>> `;; coding: utf-8-emacs-unix`, however, in windows, the file is probablly
>> in a coding of utf-8-emacs-dos. When I try to open the autoload file,
>> Emacs can't regonize the major mode which assumes to be `emacs-lisp-mode`.
>> Unless I change the `;; coding: utf-8-emacs-unix` to
>> `;; coding: utf-8-emacs`, it can be open in the `emacs-lisp-mode`.
>
>
>
>> Best Regards,
>> Shuguang Sun
>
>> In GNU Emacs 29.0.50 (build 1, x86_64-w64-mingw32)
>>  of 2022-01-31 built on YJ190169-SSG
>> Repository revision: 04f9c3b8df6afaf1e9de9f2a4478f63fd959bf09
>> Repository branch: master
>> Windowing system distributor 'Microsoft Corp.', version 10.0.19044
>> System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.1466)
>
>> Configured using:
>>  'configure --without-pop --with-native-image-api
>>  --with-native-compilation --without-compress-install
>>  '--program-transform-name=s/^ctags$/ctags.emacs/''
>
>> Configured features:
>> ACL DBUS GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES
>> NATIVE_COMP NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND SQLITE3 THREADS TIFF
>> TOOLKIT_SCROLL_BARS WEBP XPM ZLIB
>
>> Important settings:
>>   value of $LANG: CHS
>>   locale-coding-system: cp936

-- 
Best Regards
Shuguang Sun

bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows

[Michael Heerdegen]

Shuguang Sun <shuguang79@qq.com> writes:

> The issue has be fixed from the package (async) side.
> https://github.com/jwiegley/emacs-async/issues/153#event-6295734933

Thanks for confirming.  The problem didn't show up for me any more, too.
So I'm closing this report.

Thanks,

Michael.