'Terminal Command' broken?

[ranza]

I've noticed that one of my own workflows stopped working after the current update, then I've created a new workflow and experienced the same behaviour.

It seems to me that "Terminal Command" is broken. Even the most simple "ls" command freezes Alfred for about 10 sec then returns without any warning/error (just as if everything went fine).

I've even tried debugging, but it only says that a command was executed (no warnings or anything)

Alfred 2.2 (243)

OS X 10.9.3 (latest beta)

[Andrew]

 

I've noticed that one of my own workflows stopped working after the current update, then I've created a new workflow and experienced the same behaviour.

It seems to me that "Terminal Command" is broken. Even the most simple "ls" command freezes Alfred for about 10 sec then returns without any warning/error (just as if everything went fine).

I've even tried debugging, but it only says that a command was executed (no warnings or anything)

Alfred 2.2 (243)

OS X 10.9.3 (latest beta)

 

 

I've tested on a number of Macs and this appears to be instant, so there could be an issue on your Mac (Terminal / AppleScript) which is causing this issue.

 

- Can you start Terminal normally and run commands?

 

- Have you restarted your Mac in case shell has crashed?

 

Cheers,

Andrew

[ranza]

Sorry for no response, I've read it although I didn't have time to test it immediately.

It turns out it works, case closed.