Skip to content
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

Signature help not closing properly #867

Open
ulfbert-san opened this issue Oct 18, 2024 · 4 comments
Open

Signature help not closing properly #867

ulfbert-san opened this issue Oct 18, 2024 · 4 comments

Comments

@ulfbert-san
Copy link

Hello,

I've a problem, with the signature help window, it overlaps with the autocomplete window. Here is what I do:

  1. Call signature help in normal mode.
  2. Close the window with Esc or gq.
  3. Go into the insert mode and type any key between my parenthesis.

After that the signature help window is opend again + if I type a character that matches with my autocomplete, this window will open too:

Screenshot 2024-10-18 142239

But when I go to the normal mode again and then to the insert mode, it works fine and only the autocompletion is shown.

I'm glad for any help.

Greetings ulfbert

@nickspoons
Copy link
Member

Are you talking about the behaviour that was added by PR #622?

It looks like you're getting an error from asyncomplete in your screenshot, is that the actual problem here?

@ulfbert-san
Copy link
Author

I dont really understand the mentioned PR. I think I dont use the :OmniSharpFindSymbol function or do I? I'm not too deep in this topic, if I'm wrong correct me please. But I think, the problem is in the omnisharp-vim plugin. But I could be wrong.

That is how I see it: I call the signature_help function which opens a popup-window. After closing it, it should be closed and not re-open automatically.

Could this the reason why: #579 ?

Greetings ulfbert

@nickspoons
Copy link
Member

Sorry! I linked the wrong PR, I meant #662

@nickspoons
Copy link
Member

The behaviour you are describing doesn't sound quite right, no. I'm not blaming asyncomplete, but the screenshot you've shared to demonstrate the issue does have an asyncomplete error showing at the bottom, so I'm wondering if it is related - do you always get an asyncomplete error when this happens?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants