all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Shuguang Sun via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 53678@debbugs.gnu.org
Subject: bug#53678: 29.0.50; Invalid read syntax: "#<" for package install in Windows
Date: Thu, 24 Mar 2022 09:03:14 +0800	[thread overview]
Message-ID: <tencent_517DB384802D4C6BE890F8BDCF85D6633909@qq.com> (raw)
In-Reply-To: <YfmU9KvUO5cbRQD7@ACM> (Alan Mackenzie's message of "Tue, 1 Feb 2022 20:15:48 +0000")

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





  reply	other threads:[~2022-03-24  1:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  5:32 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
2022-02-01 15:00 ` Eli Zaretskii
2022-02-01 19:00   ` Arash Esbati
2022-02-02  3:32   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]     ` <yjinleyvp2xw.fsf@qq.com>
2022-02-01 20:15       ` Alan Mackenzie
2022-03-24  1:03         ` Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-03-24  1:31           ` Michael Heerdegen
2022-02-03  2:55       ` Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 19:16         ` Alan Mackenzie
2022-02-06  2:19           ` Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-06  4:08             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tencent_517DB384802D4C6BE890F8BDCF85D6633909@qq.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53678@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=shuguang79@qq.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.