-
Notifications
You must be signed in to change notification settings - Fork 394
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 working on OSX Sierra #213
Comments
Same problem. Shuttle can work with Terminal.app, but failed to start iTerm2 on Sierra. Edit: try logout/reboot your mac, shuttle might then work with iTerm2. |
I had this issue and resolved it by reinstalling shuttle with the newest version, I tested your config file worked and it worked for me. No logout / reboot required. |
Just a quick comment to say I never had any issues with Terminal and iTerm2 on Mac OS X Sierra. |
I'm seeing the same issue. Downloaded the git clone, built the program, edited the json file. It opens a new tab for each connection selected, but doesn't actually execute the ssh command. Same for Settings -> Edit: It opens the iTerm, but doesn't actually execute any command. The window title is changed, and the window appears, but no command. |
It seems I have seen a similar issue. I don't know whether this could help. I sent command or ssh to the current terminal or open a new tab. but the terminal windows just lost focus and no other things happened. Finally, I found the reason caused it is the Ubuntu VM I have installed in PD. It seems if I opened the terminal in Ubuntu VM, the command would try to send to the VM terminal rather than macOS terminal, although it failed. I solved it by canceling the VM software sharing and everything goes fine. |
I'll be installing the latest macOS this week and will test this out. @stefancrain solution should solve the issues. I'll be able to do some testing once I have latest macOS |
same issue here. |
@suxiaogang There are some applescript changes that should fix iTerm issues. You can see these changes in pull #232 I have a couple more changes that I want to include in 1.30 so I wont get to making a new binary until sometime in July. If the suggestions from @stefancrain don't work for you you'll have to use macOS terminal until the binary is released. |
In my case it was related to an old iterm2 configuration, deleting the configuration fixed the issue defaults delete com.googlecode.iterm2 |
I modified "inTerminal" in your configuration file to "current". it worked for me. I hope it helps you. |
I tried this config with Panel host. It just moves to Iterm and does nothing. Any idea why?
The text was updated successfully, but these errors were encountered: