-
Notifications
You must be signed in to change notification settings - Fork 392
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
Option to open in new window, or open multiple windows #1
Comments
+1. BTW, I just remembered the -t option of SSH that allows you to do something like change the remote directory after login, which in the case of an SSH automation like this, is quite helpful. So, I do: {
"name": "me@myserver:path/to/dir"
"cmd": "ssh me@myserver -t 'cd path/to/dir; bash --login'"
} |
A feature to open new terminal windows, instead of tabs, would be awesomes. |
This should probably just be a matter of reworking the AppleScript a little bit to change how new sessions are handled. When I wrote it, I only accommodated tabs. |
+1 To launch app and close terminal for example "cmd": "open -a Firefox 'https://myserv.admin.com'; osascript -e 'tell application "System Events" to tell process "Terminal" to keystroke "w" using command down' |
+1 |
+1 Any changes to this issue? Your App is pretty neat, and almost exactly what I searched for a long time but I really don't like Tabs when it comes to terminal sessions. |
+1 with iTerm2 I try the hidden pref It works for file not for shuttle |
@alesdotio see pull request #104
|
👍 |
Update the base fork at thshdw with the changes of head fork fitztrev
Complete! See release v1.2.3 |
Is there no option to open in tabs any more with 1.2.4?? I loved that. Now it either spits the command into the existing terminal, or opens a brand new instance which clutters up my environment depending on the inTerminal flag. |
@timothyallan If the inTerminal flag is missing then the default action is tabs. With the new version (if you are using iTerm, you must have the the |
That's why I'm here :) I got the new version, and noticed that it no longer opened new tabs. It would inject the next command into my currently open terminal window. I'd left my settings the same i.e. no inTerminal flag, as I'd not read the release notes and didn't even about it. Edit: as I type this, I'm trying again it it's opening in tabs now. Let me see if I can get a repro. |
@timothyallan Thanks for the update! 👍 Here is a draft of readme that explains the new settings: edit: |
Looks like the original issue mentioned opening multiple windows/tabs with a single menu entry, but I couldn't find anything in the Command Settings wiki page describing the syntax for that. Is that supported? |
@stephenhandley see here https://github.com/fitztrev/shuttle/wiki/Command-Settings#interminal-value
If this is not what you are looking for could you provide an example of what you would like to accomplish? |
@thshdw Thanks but I don't think that answers my question. I'm asking how to open 2 windows with one menu entry. For example, I want to open an ssh tunnel in one window and then run |
@stephenhandley are you running the postgres command on the same server you are ssh'ing too? |
@thshdw nope running it locally. again this is just one example, I could think of others: open docker logs in one window and run tests in another |
@stephenhandley Thanks for clarifying. Are you using iTerm and want these in multiple panes? Or are you using terminal and want them in separate windows? |
@thshdw i'm using terminal. multiple tabs within the same window would be awesome, but multiple windows works if the former isn't possible. |
@stephenhandley How would you feel about moving the conversation here: #172 |
@thshdw sounds good. |
Hey, neat little app! It would be really cool if you could add some more options though. I would personally like if there was a way to open new terminal windows instead of tabs, or to even have one menu entry open multiple windows.
For example:
which would open two windows, one sshing to the server and the other opening a local directory.
The text was updated successfully, but these errors were encountered: