From: "João Távora" <joaotavora@gmail.com>
To: mprodrigues@posteo.net
Cc: emacs-devel@gnu.org
Subject: Re: 30.0.50; 'New' error message when using eglot
Date: Tue, 28 Feb 2023 12:42:23 +0000 [thread overview]
Message-ID: <877cw2q7v4.fsf@gmail.com> (raw)
In-Reply-To: <528de6a43ed72cfeb943216fea8c2352@posteo.net> (mprodrigues@posteo.net's message of "Tue, 28 Feb 2023 11:05:18 +0000")
mprodrigues@posteo.net writes:
> Hello,
>
> I have the same problem.
>
>> emacs -Q --eval '(add-hook (quote python-mode-hook) (function
>> eglot-ensure))' ~/tmp/coiso.py
>
> If I use this it works, so maybe the bug is coming from interactions
> with other packages?
It would surely seem so, as eglot.el doesn't have very many plist-member
calls, and none of them for the ':signatures' key.
So someone is going to go throught the trouble of making a reproducible
error recipe (or bisecting a configuration), otherwise I can't be of
much help.
> I did M-x toggle-debug-on-error so we can get a backtrace, and this is
> what I got:
>
> Debugger entered--Lisp error: (wrong-type-argument plistp [])
> plist-member([] :signatures)
> #f(compiled-function (jsonrpc-lambda-elem10) #<bytecode
> 0xdcf9bf12d010fe5>)([])
> jsonrpc-connection-receive(#<eglot-lsp-server
> eglot-lsp-server-186e364> (:jsonrpc "2.0" :id 44 :result []))
> jsonrpc--process-filter(#<process EGLOT (mprodrigues/(python-mode
> python-ts-mode))> "Content-Length: 37\15\nContent-Type:
> application/vsco...")
It would also help to see what the the client request for :id 44 was in
the first place. You could find that in the buffer brought to you by
M-x eglot-events-buffer
João
next prev parent reply other threads:[~2023-02-28 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 11:05 30.0.50; 'New' error message when using eglot mprodrigues
2023-02-28 12:42 ` João Távora [this message]
2023-02-28 13:58 ` mprodrigues
2023-02-28 14:28 ` João Távora
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 7:36 Pedro Andres Aranda Gutierrez
2023-02-23 21:30 ` João Távora
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=877cw2q7v4.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mprodrigues@posteo.net \
/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.