From: Dmitry Gutov <dmitry@gutov.dev>
To: Troy Brown <brownts@troybrown.dev>, 74914@debbugs.gnu.org
Cc: "Felician Nemeth" <felician.nemeth@gmail.com>,
"João Távora" <joaotavora@gmail.com>
Subject: bug#74914: 30.0.90; Eglot: Incorrect parameter highlighted in signatureHelp
Date: Sun, 29 Dec 2024 05:22:48 +0200 [thread overview]
Message-ID: <53ccf716-7ca6-476f-af39-36300f0a7f1e@gutov.dev> (raw)
In-Reply-To: <CABvCZ439epBgvmmfL5LezrV0vcR0DinG_g5w=9MEz3q6So3PjQ@mail.gmail.com>
Hi!
On 16/12/2024 17:19, Troy Brown wrote:
> I believe the reason for Eglot's behavior is due to the way
> "active-param" is specified in the cl-loop within `eglot--sig-info`.
> ```text
> with active-param = (or sig-active activeParameter)
> ```
> The value of activeParameter in SignatureInformation (activeParameter)
> should be given higher priority (i.e., listed first) over the
> activeParameter specified in SignatureHelp (sig-active).
So, does this fix the problem for you?
diff --git a/lisp/progmodes/eglot.el b/lisp/progmodes/eglot.el
index 816a1e67eca..51c19d5681a 100644
--- a/lisp/progmodes/eglot.el
+++ b/lisp/progmodes/eglot.el
@@ -3416,7 +3416,7 @@ eglot--sig-info
'font-lock-function-name-face))))
;; Now to the parameters
(cl-loop
- with active-param = (or sig-active activeParameter)
+ with active-param = (or activeParameter sig-active)
for i from 0 for parameter across parameters do
(eglot--dbind ((ParameterInformation)
((:label parlabel))
prev parent reply other threads:[~2024-12-29 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 15:19 bug#74914: 30.0.90; Eglot: Incorrect parameter highlighted in signatureHelp Troy Brown
[not found] ` <handler.74914.B.173436237328655.ack@debbugs.gnu.org>
2024-12-23 15:54 ` bug#74914: Acknowledgement (30.0.90; Eglot: Incorrect parameter highlighted in signatureHelp) Troy Brown
2024-12-28 11:33 ` bug#74914: 30.0.90; Eglot: Incorrect parameter highlighted in signatureHelp Eli Zaretskii
2024-12-28 13:28 ` João Távora
2024-12-29 3:22 ` Dmitry Gutov [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53ccf716-7ca6-476f-af39-36300f0a7f1e@gutov.dev \
--to=dmitry@gutov.dev \
--cc=74914@debbugs.gnu.org \
--cc=brownts@troybrown.dev \
--cc=felician.nemeth@gmail.com \
--cc=joaotavora@gmail.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.