-
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
Installer freezes when testing custom Atom editor command while Atom is already open #3155
Comments
Hmm. This is the code that runs that test: https://github.com/git-for-windows/build-extra/blob/7d6d0dfbfbacb55ad7af8d76a7c88f85db9f80bf/installer/install.iss#L1505-L1560 From what you say, it is probably stuck here: https://github.com/git-for-windows/build-extra/blob/7d6d0dfbfbacb55ad7af8d76a7c88f85db9f80bf/installer/install.iss#L1529 |
Oh... would you have a chance to test out something? I have the hunch that calling the This is how you can help by testing it:
|
That seems to do the trick and I created a pull request. I assume this won't lead to problems with editors that are installed system-wide? I have no experience here. |
installer: use ShellExecAsOriginalUser() instead of ShellExec() for custom editor tests This is the right thing to do: if the editor in question wants to communicate via IPC to a user-specific instance, it will _have_ to be run as original user. Atom would be such an editor, and it was reported in git-for-windows/git#3155 that this is indeed required to Make Things Work. Signed-off-by: Johannes Schindelin <[email protected]>
Fixed via git-for-windows/build-extra#334 |
When testing a custom editor in the installer, [we now spawn it in non-elevated mode](git-for-windows/git#3155), fixing e.g. Atom when an instance is already running. Signed-off-by: Johannes Schindelin <[email protected]>
Setup
Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
What options did you set as part of the installation? Or did you choose the
defaults?
Any other interesting things about your environment that might be related
to the issue you're seeing?
Nope.
Details
How did I produce the error?
atom --wait --new-window
.What happened?
The text was updated successfully, but these errors were encountered: