Odd Terminal.app Tab Behavior when Command is Sent from Alfred.app

[apm]

So some odd behavior when using the > trigger to send a Terminal.app command via Alfred.

 

How to replicate:

1. Send a command to Terminal.app via Alfred (e.g. >top)
2. When Terminal.app opens with top running, open a new tab (⌘+t)
3. 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

[Andrew]

So some odd behavior when using the > trigger to send a Terminal.app command via Alfred.

 

How to replicate:

1. Send a command to Terminal.app via Alfred (e.g. >top)
2. When Terminal.app opens with top running, open a new tab (⌘+t)
3. 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