-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
OSAScript launch commands in OS X .dmg can behave incorrectly if user has a Parallels VM with a terminal open #14427
Comments
The script could target the Terminal.app application more precisely using something like this:
Would this avoid using the ambiguous "Terminal"? I use iTerm rather than Terminal, so I don't use the Julia app anyway... |
I simplified the script a fair bit recently. I can try this out and update accordingly. Seems like it should solve this one. @dljsjr Would this fix your issue? |
@ViralBShah Using the bundle ID seems to work well when I test it locally. |
Fixed by #18522, please reopen if this is not the case. |
(cherry picked from commit 329e7e1) ref #18522 include fix for #14427 (cherry picked from commit 259e174) expand README (cherry picked from commit 399710e) remove use of sudo from OS X app makefile (cherry picked from commit 55fa673) add recommended Info.plist keys (cherry picked from commit aeadb11)
This is a weird edge case bug and probably not worth spending a lot of cycles on, but I figured I'd report it anyway.
The current mechanism for launching the Julia REPL uses an OSAScript command (as seen here: https://github.com/JuliaLang/julia/blob/ac8f4f1ebc2bd0ccf0840cdee27830becbcf39a7/contrib/mac/app/script) to launch Terminal.app
If a user is running Parallels, either in normal mode or Coherence mode, and there is a virtual machine running that just so happens to have an app called "Terminal" running, then the commands that reference Terminal.app by name may inadvertently pick up on the VM's "terminal" app due to Parallels exposing apps running on the VM to the host OS for ease-of-use.
The bare minimum for showing that Parallels is what is responding to the OSAScript actions instead of system Terminal.app is to launch an Ubuntu VM in Parallels and use the stock Terminal application in Ubuntu. For added drama, disable Coherence but use OS X's full-screen mode or put the VM window in a different Space/Desktop. Then run the following simple AppleScript:
Your Desktop/Space will swap to the virtual machine and the virtualized terminal will gain focus.
Environment:
Steps to reproduce:
Expected results:
Terminal.app launches with the Julia REPL configured and running in OS X Terminal.app
Actual results:
Terminal.app is not launched, Terminal in the virtual machine is given focus.
The text was updated successfully, but these errors were encountered: