-
Notifications
You must be signed in to change notification settings - Fork 30
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
LustyExplorer Horizontal Splits #52
Comments
Sounds like you are requesting that the splits maintain their relative proportions when the explorer is active? |
I am also seeing this issue. It's especially annoying when you have a quickfix window open as a bottom split because lusty will cause the entire screen to jump up and disrupt your vision. The standard behavior of opening a split, as far as i know automatically retains equal proportions. So when yo open the lusty split, you should just do a regular split and then resize it to whatever size it should be. Everything else will be maintained by default (I think). So maybe lusty is doing something sort of custom there. I haven't looked at the code yet. |
Any updates on this? It's sort of irritating to me also and if someone else has already figured out a fix, I'd love to see a patch... |
I'm a little overextended these days so probably won't have time to fix this myself, but I'd be happy to accept a patch. :-) |
No worries, I'll take a look this evening and see what I can do in the way of a patch. |
Fixed by pygatea. |
mkdir ~/test-lusty-bug
cd ~/test-lust-bug
Open vim.
Create two buffers a.txt and b.txt and split horizontally (a.txt open in top 50%, and b.txt open in bottom 50%)
:ls
2 %a "b.txt" line 1
3 a "a.txt" line 0
Press leader and lr to open Lusty Explorer
You'll see that the heights of a.txt and b.txt are not maintained, rather a.txt shrinks to 1 line visible and b.txt now takes whole view (minus lusty window at bottom). Cancelling returns to normal but this is an annoyance as I can no longer study most of real estate when opening lustyexplorer.
The text was updated successfully, but these errors were encountered: