-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable #_calling: in hover #1954
Labels
Comments
Oops, opened this under my work account. |
I agree this could be configurable, we could leverage this existing boolean to check for a |
Cool, I'll take a crack at adding it. |
NoahTheDuke
added a commit
to NoahTheDuke/clojure-lsp
that referenced
this issue
Jan 24, 2025
Defaults to false. If true, doesn't include `#_calling: user/foo [x y z]` at the start of hover text. Closes clojure-lsp#1954
3 tasks
ericdallo
pushed a commit
that referenced
this issue
Jan 24, 2025
* Add :hover :hide-signature-call setting Defaults to false. If true, doesn't include `#_calling: user/foo [x y z]` at the start of hover text. Closes #1954 * bb lint-fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
As implemented after discussion in #1281, hovering a local shows a line indicating the surrounding calling context:
Requesting hover will show:
I don't want or need the first line of information. It is distracting and noisy. If I needed to see the signature of the surrounding call, I'd move to it and look at it, or I'd trigger signatureHelp.
Describe the solution you'd like
Add a config option to not show this.
Describe alternatives you've considered
Additional context
I use neovim so I can get hover without editing text, which maybe gives me a different perspective than in other editors where there's no difference. But for me it's very distinct: when I am moving around and reading code, I want only the documentation for a given variable. When I'm editing code, I want the signatureHelp. There's no need for overlap.
The text was updated successfully, but these errors were encountered: