Splits with WinBar change size when opening and closing FZF
- Dominant language
- Vim Script
- Stars
- 10.3k
- Forks
- 608
- Avg merge
- 5d 8h
- Merged PRs (30d)
- 2
Description
# Splits with WinBar change size when opening and closing FZF
- [x] I have fzf 0.30.0 or above
- [X] I have read through https://github.com/junegunn/fzf.vim/blob/master/README.md
- [X] I have read through https://github.com/junegunn/fzf/blob/master/README-VIM.md
- [X] I have read through the manual page of fzf (`man fzf`)
- [X] I have searched through the existing issues
## Description
If a split has a WinBar, opening and closing FZF in the split above it causes it to shrink.
Video demonstration of this bug: https://asciinema.org/a/nYiOnge1cr5FXbbAcc4pLZGF6
## How to reproduce
1. Launch vim with `vim --clean -Nu <(curl https://gist.githubusercontent.com/junegunn/6936bf79fedd3a079aeb1dd2f3c81ef5/raw)`
2. Wait for vim-plug to install everything
3. Close the split created by vim-plug so that the window contains one empty split
4. Split the window horizontally, such that there are two splits, one above the other
5. Switch to the BOTTOM split
6. In the BOTTOM split, run the following vim command in order to create a WinBar: `:nnoremenu 1.10 WinBar.Step :Step`
7. Switch to the TOP split
8. In the TOP split, run the following vim command: `:FZF`
9. Press `ESC` to close the FZF popup
## Expected behavior
The sizes of the two splits stay the same
## Actual behavior
The bottom split shrinks by one line. Repeating the last two steps keeps on shrinking the split, until it becomes unusably small.
## Why would anyone care?
Vimspector is another popular plugin that uses WinBar heavily. This issue is a major inconvenience for people who want to use Vimspector and fzf.vim together. They are left with three chpices: disabling WinBar support in Vimspector (`let g:vimspector_enable_winbar=0`); constantly re-adjusting the size of their splits; or trying to avoid using fzf when debugging. None of these are satisfactory.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.