From: hiecaq <this@hiecaq.org>
To: 70211@debbugs.gnu.org
Cc: Lilly <lilly.ra@proton.me>
Subject: bug#70211: emacs-eglot fails after upgrade to emacs-29.3
Date: Sat, 13 Apr 2024 18:58:57 +0800 [thread overview]
Message-ID: <875xwlbkb2.fsf@hiecaq.org> (raw)
In-Reply-To: <87cyqxs25l.fsf@hiecaq.org> (hiecaq's message of "Wed, 10 Apr 2024 22:49:58 +0800")
Lilly via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> Upgrading jsonrpc to version 1.0.25 solved the issue for me.
Hi, the above solution does not work for me so I tried to dig into
the problem further, and I think I've moved closer to the real
cause of this problem.
TLDR:
This issue is more close related to jsonrpc instead of eglot, and
putting
> (setq load-no-native t)
In early-init.el fixes the problem for me.
The first thing I noticed is that if we look up
"jsonrpc-connection", Help page tells us that it is a
native-compiled function, which is the hint to my following
attempts because in my configurations packages are only
byte-complied and not native-compiled, while built-ins are
native-compiled. This can be quickly checked if you open the
jsonrpc.elc file. (and I believe that it is the same case for the
upstream Guix)
Also, if you visit the "jsonrpc-connection"'s class Help page, it
shows that it does not have a slot named
"events-buffer-config". Instead it has
"events-buffer-scrollback-size", which reflects the corresponding
file in 29.3 built-in.
So my guess is that Emacs somehow prefers the native-compiled
version (from the built-in) over the byte-compiled version (from
the package), even if the latter is newer. I do have "(setq
load-prefer-newer t)" in my early-init.el, but it still works that
way. I'm not sure why the package loading works as expected before
recent updates in Guix though.
prev parent reply other threads:[~2024-04-15 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 7:25 bug#70211: emacs-eglot fails after upgrade to emacs-29.3 Lilly via Bug reports for GNU Guix
2024-04-10 14:49 ` hiecaq
2024-04-13 10:58 ` hiecaq [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xwlbkb2.fsf@hiecaq.org \
--to=this@hiecaq.org \
--cc=70211@debbugs.gnu.org \
--cc=lilly.ra@proton.me \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).