-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
GIT_EDITOR set to .sh
script on windows
#153246
Comments
@wookie184, apologies for not gettig back to you on this. In the latest Stable and Insiders versions, the |
Thanks for the reply. That does prevent the issue, although my use case is more that I want to use VSCode as my git editor, but for the |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
.sh
script on windows.sh
script on windows
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
$Env:GIT_EDITOR
in vscode powershell terminal."c:\Users\wookie184\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\extensions\git\dist\git-editor.sh"
. AFAICT.sh
files are not valid executables on windows so this doesn't make much sense.This causes issues when running external tools (e.g. https://pypi.org/project/blurb/) which try and use
GIT_EDITOR
themselves. This can be avoided by disabling VSCode as your git editor ("git.useEditorAsCommitInput": false
) but it would be nice to not have to do this.I'll create an issue in
blurb
as well but I think it would be much better if it could be fixed here if possible as I'd guess there are many other tools that useGIT_EDITOR
. (I don't thinkblurb
could do much more than using a fallback if the env variable fails).Thanks!
The text was updated successfully, but these errors were encountered: