-
Notifications
You must be signed in to change notification settings - Fork 491
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
Neovide hover popup overflows the window edge to the right/bottom and not staying within window boundaries #1641
Comments
This is probably fixed by #1786 |
@fredizzimo Just tested with master branch and result is still the same. |
This looks like a Neovim bug, according to the logs it does not report the correct position. I will report the bug on their issue tracker. It might be possible that we are expected to do the positioning ourselves, but let's see what the response is first. I think it's this code that is the problem |
This Neovim issue has been crated neovim/neovim#24801 |
This will be fixed by #2029. But it would still have been better for Neovim to deal with it. |
Describe the bug
When hovered over method / function / struct etc declaration the hover box overflows over the right screen edge when opened with neovide. But when same operation is performed with neovim using terminal or in this case KDE's konsole the hover will not overflow the screen edge but stays withing the window boundaries.
I am aware there was previously bug related it overflowing to the left, but did not find a issue related it bleeding to the right of the window.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The hover should stay within the window boundaries and not overflow to the right.
Screenshots
Desktop (please complete the following information):
Please run
neovide --log
and paste the contents of the.log
file created in the current directory here:Additional context
Attached log files since the content would be too large to paste in this thread.
neovide_r2022-11-18_00-39-32.log
neovide_rCURRENT.log
The text was updated successfully, but these errors were encountered: