-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
“Not a valid executable” error in installer #1951
Comments
https://github.com/git-for-windows/build-extra/blob/4dd83144dc06971722cbf83406b2f2f8ae9f9916/installer/install.iss#L1147 |
Oh, that is actually worked, thank you, @linquize! ❤️ I tried to provide full path to I will probably leave this issue open as the improvement suggestion: there probably no need in using |
@DaFri-Nochiterov unfortunately, times are pretty frantic over here, so I need to ask you to do more than just leave this issue open. Could you extend the code indicated by @linquize to test also for |
@dscho If the issues is not taken up yet, can I work on it? |
@aakiiti-jain if @DaFri-Nochiterov isn't able to offer a PR, then Go For It (TM). Contributions are welcome, as per #1951 (comment) |
Yeah. I'm not familiar with language and tools, so it'll take me much time to learn to know all the stuff so to make any PR. This is also almost Christmas and there are many things to do atm. So yeah, if you want to make a PR — do it, please! <3 |
@aakriti-jain go for it! ;-) |
This should be addressed by git-for-windows/build-extra#221 |
Setup
Details
When configuring installation, there is option to select the other git editor.
When I type out the
code-exploration -w
in the field, I expect it to run the Visual Studio Code exploration once I click “Test Custom Editor” and then allow me to proceed to installation.When I press the button it says “Not a valid executable: "cod".” No matter how you try to type the path or command, it will throw an error, I tried literally everything possible, including
/d/Main/…
,D:\Main\…
,"D:\Main\…"
and selecting the binary via the “Browse…” button after field.The text was updated successfully, but these errors were encountered: