Jump to content

Recommended Posts

Posted

When I type > followed by a shell command and hit enter, Alfred command window disappears but nothing else happens, terminal doesn't open and command is not executed. This feature used to work, but I'm not sure after which upgrade it broke.

 

I have iTerm2 installed so I tried changing terminal app setting, and changing prefix – no result.

 

Only when I switched to "Custom" setting (and left default Action Script snippet) it worked again.

 

OS X 10.10.1 (14B25)

Alfred v2.5.1 (308)

Posted

I've just confirmed that it works on my end. Have you tried redownloading and installing Alfred? All your data will be saved, and this will fix the issue if there are any corruptions in the current file.

Posted

iTerm2 has overhauled its AppleScript support which makes Alfred 2 currently incompatible. This is something I'm currently looking into, but the default Terminal support should work fine!

 

Cheers,

Andrew

Posted

Try setting the Terminal to "Custom" in Alfred's Features > Terminal, and setting the script to:

on alfred_script(q)
    tell application "iTerm"
		activate
		set _term to (make new terminal)
		tell _term
			launch session "Default"
			tell current session
				write text q
			end tell
		end tell
    end tell
end alfred_script
  • 2 weeks later...
Posted

I thought I'd post this here in case anyone else finds it useful.  I use ZOC as my terminal application and the following custom code works for Alfred terminal commands:

on alfred_script(q)
  tell application "zoc6"
    activate
    start conversation
      perform "ZocSend" using q
      perform "ZocSend" using "^M"
    end conversation
  end tell
end alfred_script

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...