-
Notifications
You must be signed in to change notification settings - Fork 94
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
[BUG] Startup broken on MSYS2 #241
Comments
How about |
@Aloxaf |
@Aloxaf All this was tested on a brand new MSYS install with an empty .zshrc and the newest commit you pushed 4 hours ago. Extra frustrating is the fact, that I can't even get fzf to work properly half of the time. On one computer it works in alacritty but fails in the MSYS' provided mintty (Upon executing fzf it get's stuck in a manner similar to msys2/MINGW-packages#10113 (comment) ). On another one it suddenly stopped working in Alacritty as well. That needs some extra investigation I guess, but is hopefully not relevant to this issue. |
it's
which version of fzf are you using? msys fzf or windows native fzf? |
Ohhhhh. Yeah that works. The log looks a bit bare though:
I am using not the windows native version. Since the there is no fzf in either the MSYS packages or the MinGW64 packages, I installed it via git manually as described in the docs here: https://github.com/junegunn/fzf#using-git |
try put these lines to your zshrc (assuming your are using zinit)
|
reported to upstream: junegunn/fzf#2680 |
Please update and try again |
Describe the bug
I use MSYS2 with the MinGW64 environment and the ZSH shell. Installting fzf-tab fails, because running
source ~/somewhere/fzf-tab.plugin.zsh
results infzf-tab.plugin.zsh:1: command not found: fzf-tab.zsh
This does not only concern the automatic install method. Same with zinit, see screenshot:
I am not even sure how to debug this. Clearly fzf-tab.zsh is there...
I can make sure:
compinit
Environment:
Minimal zshrc
Literally empty
Same after installing zinit
Log
Failed to load, so no fzf-tab logs
The text was updated successfully, but these errors were encountered: