-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
When used on a line with flycheck error, lsp-ui can add an empty line before the popup #1292
Comments
BTW, i can saw candidate is visible at first, but then disappear after a flash |
You should probably file it with But also see #1285 which seems related, and the author ended up finding something in their config (or maybe an additional package) which caused the problem. |
Okay, i try reproduce this issue use a minimum config, and finally, i find out the reason cause this: (setq truncate-partial-width-windows t) When above variable set to t, i can reproduce this behavior. When i comment it out to use default value nil, i can get following strange behavior. if i entering then remove As you can see, it add a blank line after File. this issue seem like only happen when I can reproduce this issue even no flycheck or enable my theme, so, i will create a issue LSP there, and reference this, thank you. |
This issue should not related to company? i guess, it caused by following config:
So, closing it ... |
Thanks for the investigation. There might be something we can/should fix here. Can you reproduce this with the latest Company master? Which version are you using? Can you reproduce this without LSP? Say, inside an Does Flycheck have to be enabled? Does it happen with Flymake too? |
Yes, i use f481c1e
No, In fact, i guess because some config issue, company no meanful candidate for most of my code, i still try figure those things out, but, anyway, i test it
Yes, it can reproduce when work with builtin flymake. BTW, this issue moved by lsp maintainer into lsp-ui, emacs-lsp/lsp-ui#679 and @yyoncho said, using company-posframe will fix the issue, though, i still never try it. |
Yes, of course. It uses a child frame, so it's not affected by any buffer contents. Anyway, it seems like a company<->lsp-ui conflict, rather that a fundamental bug here. Let's see if lsp-ui's maintainers will have any further ideas. Thanks. |
I create a issue here too, but i consider maybe this is a company issue?
The text was updated successfully, but these errors were encountered: