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

Blamer doesn't work with Windows Powershell #50

Open
zhengrc19 opened this issue Nov 2, 2021 · 1 comment
Open

Blamer doesn't work with Windows Powershell #50

zhengrc19 opened this issue Nov 2, 2021 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@zhengrc19
Copy link

This is my first issue ever written so please correct me if I'm formatting something wrong.

I am a Windows 10 user with Neovim 0.5.0. Everything was working great with blamer.nvim, until I added the line set shell=powershell.exe in my vimrc. Seems like there are some differences between cmd.exe and powershell.exe, which made blamer stop working and return this:

[blamer.nvim] An unknown element "" was received. This can happen if the remote process closed or ended abnormally.

This line is printed in the command line with Press ENTER or type command to continue below, so I'm basically unable to do any more operations before pressing ENTER and that makes Neovim unusable. Currently I deleted the line of setting the shell to powershell.

I also found this issue from vim-gitgutter that seems to have fixed the exact same problem by somehow forcing use of cmd.exe in the plugin. Maybe it would be simply a few more lines of code for the developer to add in? I know pretty much nothing about Vimscript so I don't know which part of the commit to add and where to add.

@georgesofianosgr
Copy link
Collaborator

Hello @zhengrc19 . We don't use Windows so it is impossible to implement a fix and test it.
But if anyone wants to try and fix it we will accept a pull request :)

@georgesofianosgr georgesofianosgr added bug Something isn't working help wanted Extra attention is needed labels Jan 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants