Skip to content
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

Using vim list as source in pwsh will cause 'Command failed: type .....' #3517

Open
5 of 11 tasks
kevyuu opened this issue Nov 28, 2023 · 3 comments
Open
5 of 11 tasks
Labels

Comments

@kevyuu
Copy link

kevyuu commented Nov 28, 2023

  • I have read through the manual page (man fzf)
  • I have the latest version of fzf
  • I have searched through the existing issues

Info

  • OS
    • Linux
    • Mac OS X
    • Windows
    • Etc.
  • Shell
    • pwsh
    • bash
    • zsh
    • fish

Problem / Steps to reproduce

Type :call fzf#run({'source':['test1', 'test2']}) in neovim.
Error output:
fzf

@kevyuu
Copy link
Author

kevyuu commented Nov 28, 2023

setting $env:SHELL to cmd.exe fix the issue. Seems like there is logic error when escaping the path. powershell don't use ^ as escape character unlike cmd.exe

@kevyuu kevyuu changed the title Using vim list as source in windows will cause 'Command failed: type .....' Using vim list as source in pwsh will cause 'Command failed: type .....' Nov 28, 2023
@harshad1
Copy link

harshad1 commented Feb 2, 2024

This happens to me intermittently. Closing vim and reopening it sometimes fixes the issue. (Perhaps something to do with the temp file name?)

I have as yet not found a way to consistently reproduce it.

@junegunn
Copy link
Owner

Can you update fzf and fzf.vim to the latest and check if it helps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants