-
Notifications
You must be signed in to change notification settings - Fork 676
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
feature request: fixed search pane height #306
Comments
Would moving the match window to the top of the screen work for you? The top hit won't jump around if the match window is at the top. You can have this by setting |
I think it could work. In general I also like the idea of a fixed window height (whether it's at the top or bottom) so my eyes aren't drawn to something that looks like it's moving around. But whatever's the lower hanging fruit! On Oct 25, 2012, at 8:33 PM, kien notifications@github.com wrote:
|
I second this, as it would allow to achieve the same behavior as pentadactyl completion list, although I'd rather having it working ctrlp's way, so I've just sent a message to the mail list. |
I believe the ideal solution would be that, when docked to either the top or the bottom, the search results change height, but they never upset your buffer lines. For the bottom docking, it already works correctly. For the top docking, a results pane of height 10 would need to be shown by adjusting the buffer lines by -10, to give the appearance that the results are "overlayed" in a layer on top of the buffer. Does anyone know how to make this work? |
thanks, this is great! |
I'd love to see an option for a fixed height for the search pane. I prefer to have the top hit show up at the top, but I don't like that position jumping around based on the number of results. I'd like the pane to always be the height of my ctrlp_max_results, even if there are fewer or no results.
Let me know if this is possible and I just missed it in the options; thanks for the very useful plugin.
The text was updated successfully, but these errors were encountered: