Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Not working if iTerm2 sends text at start #147

Open
olalonde opened this issue Oct 28, 2016 · 5 comments
Open

Not working if iTerm2 sends text at start #147

olalonde opened this issue Oct 28, 2016 · 5 comments

Comments

@olalonde
Copy link

screenshot 2016-10-28 16 08 36

mcfsk7uiwa

Is there any way to get Kube-Solo to use the window started by tmux and/or be able to configure a non default iTerm2 profile which will be used?

@rimusz
Copy link
Member

rimusz commented Oct 30, 2016

The default Terminal would be easier to be used instead of tmux
The required terminal app could be stored in some settings file and used opening shell scripts

@olalonde
Copy link
Author

olalonde commented Oct 30, 2016

Indeed. Trying to make it work with tmux seems like a bit of a PITA. Another option would be to see if a flag can be passed to open -a iTerm.app "$1"/first-init.command to tell iTerm to ignore the "send text at start" setting. That would probably be ideal. What do you think? (asked here https://gitlab.com/gnachman/iterm2/issues/5288)

@olalonde
Copy link
Author

Looks like another way would be to chose a profile called "kube-solo" if it exists and otherwise use the default profile: https://www.iterm2.com/documentation-scripting.html. That way, I could create a "kube-solo" profile which doesn't send text at start.

@olalonde
Copy link
Author

olalonde commented Nov 3, 2016

Oh, looks like there will be a new option in iTerm to "disabled text at start when opening a script" https://gitlab.com/gnachman/iterm2/issues/5288. 👍

@rimusz
Copy link
Member

rimusz commented Nov 3, 2016

ok, cool

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants