Skip to content

Setting lsp-signature-auto-activate has no effect until lsp--update-signature-help-hook is ran manually #4748

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

Open
3 tasks done
Atemu opened this issue Mar 31, 2025 · 0 comments
Labels

Comments

@Atemu
Copy link

Atemu commented Mar 31, 2025

Thank you for the bug report

  • I am using the latest version of lsp-mode related packages.
  • I checked FAQ and Troubleshooting sections
  • You may also try reproduce the issue using clean environment using the following command: M-x lsp-start-plain

Bug description

Title.

Steps to reproduce

  1. Execute action that causes on-char signature display
  2. See huge minibuffer taking up most of the screen
  3. (setq lsp-signature-auto-activate nil)
  4. Execute action that causes on-char signature display
  5. Still see huge minibuffer taking up most of the screen
  6. lsp--update-signature-help-hook
  7. Execute action that causes on-char signature display
  8. No more minibuffer

Expected behavior

I should be able to set one variable that authoratively determines signature display auto activation.

Which Language Server did you use?

rust-analyzer

OS

Linux

Error callstack

Anything else?

No response

@Atemu Atemu added the bug label Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant