fzf.vim Shows Blank Screen in Git Bash on Windows
- Dominant language
- Go
- Stars
- 83k
- Forks
- 2.9k
- Avg merge
- 17h 8m
- Merged PRs (30d)
- 10
Description
### Checklist
- [X] I have read through the manual page (`man fzf`)
- [X] I have searched through the existing issues
- [ ] For bug reports, I have checked if the bug is reproducible in the latest version of fzf
### Output of `fzf --version`
0.56.0 (ff16877)
### OS
- [ ] Linux
- [ ] macOS
- [X] Windows
- [ ] Etc.
### Shell
- [X] bash
- [ ] zsh
- [ ] fish
### Problem / Steps to reproduce
Description:
Screenshot

Hello everyone,
I’m encountering an issue when trying to use fzf.vim in Git Bash on Windows. When I run :Files (or other fzf.vim commands) in Vim, it just shows a blank screen, as seen in the attached screenshot.
System Details:
Operating System: Windows 10
Shell: Git Bash (using MinGW64)
Vim version: version 9.1.532
Git version: Git-2.46.0-64-bit
fzf I confirmed it works in Git Bash when I use the alias fzf="winpty fzf".
Problem Summary: fzf works on the command line with the alias fzf="winpty fzf", but when I try to use it through fzf.vim (e.g., :Files), the screen is blank in Vim.
Steps Tried:
Alias: I added alias fzf="winpty fzf" to get fzf working in Git Bash.
Testing on Command Line: Running fzf on its own in Git Bash works fine, showing a list of files or results as expected.
Using fzf.vim in Vim: When I execute :Files, the screen is blank and unresponsive.

Additional Details:
Has anyone encountered this issue, or does anyone have suggestions for getting fzf.vim to work correctly in Git Bash on Windows? I’ve been stuck on this for quite some time, and any help would be appreciated.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the blank screen with fzf.vim’s :Files command in Git Bash on Windows, using the reported Vim, Git, and fzf versions, and verify the latest fzf version as well. Compare this with the working command-line alias; done means fzf.vim displays and accepts results normally instead of becoming blank and unresponsive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, vim
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100