apm Posted July 16, 2015 Share Posted July 16, 2015 So some odd behavior when using the > trigger to send a Terminal.app command via Alfred. How to replicate: Send a command to Terminal.app via Alfred (e.g. >top) When Terminal.app opens with top running, open a new tab (⌘+t) Note that the new Terminal.app tab opens and also automatically executes top I've verified that if you open Terminal.app, run a command, then open a tab, the first tab's command is not automatically executed in the new tab. Cheers, Andrew Alfred, 2.7.1 (387) System Version: OS X 10.10.4 (14E46) Kernel Version: Darwin 14.4.0 Boot Volume: Macintosh HD Boot Mode: Normal Link to comment
Andrew Posted August 25, 2015 Share Posted August 25, 2015 So some odd behavior when using the > trigger to send a Terminal.app command via Alfred. How to replicate: Send a command to Terminal.app via Alfred (e.g. >top) When Terminal.app opens with top running, open a new tab (⌘+t) Note that the new Terminal.app tab opens and also automatically executes top I've verified that if you open Terminal.app, run a command, then open a tab, the first tab's command is not automatically executed in the new tab. Cheers, Andrew Alfred, 2.7.1 (387) System Version: OS X 10.10.4 (14E46) Kernel Version: Darwin 14.4.0 Boot Volume: Macintosh HD Boot Mode: Normal Sorry for the delay in reply to this... the issue and solution is posted in this thread: http://www.alfredforum.com/topic/1291-terminal-action-repeats-when-opening-new-tabs/ You need to set new tabs to open with "Default Profile" in Terminal.app's General preferences! Cheers, Andrew Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now