-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
number of results displayed in minibuffer shrinks after visiting a long multi-line result #1807
Comments
Thanks very much for your detailed reply! I am running emacs in the terminal and as it turns out I'm getting the exact same behavior that you described above. I was wrong when I said the number of displayed entries is reduced, it is just that the mini-buffer grows leaving an awkward blank area as you described. Setting Thanks and apologies for the confusion! |
I'm glad to hear. I noticed an issue when |
FWIW, there also exist the commands |
This issue manifests when scrolling through the ivy minibuffer after running something like counsel-rg which could contain very long matches. Upon visiting a match that is long enough that it exceeds the width of the minibuffer and then scrolling past is such that all results currently displayed each fit on one line, the number of displayed results is reduced by one.
Here is a simple reproducer. Initially 5 results are displayed but once you visit the long line, only 4 results are displayed for the remaining life of the minibuffer.
My desired behavior here is that once we pass the long entry, we go back to displaying 5 single line entries.
(setq ivy-height 5)
(ivy-read "test: " '( "one" "two" "four" "five" "six" "seven" "eight" "ttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt
tttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt
ttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt" ))
The text was updated successfully, but these errors were encountered: