vitor

I didn't want to use applescript because my last workflow used it and it was a pain.

I know the feeling — a mix between “I hate this” and “at least there’s some way to do it”.

Another update, regarding the last one. More corrections regarding special characters.

You can do it with Applescript (to run applescript inside your bash script, use osascript -e "<code here>").

-- with this method
-- if a Finder window is the frontmost window, it’ll return the path to it, else it’ll return the path to the desktop

tell application "Finder" to set dirPath to (quoted form of POSIX path of (insertion location as alias))

return dirPath

-- with this method
-- if there’s any Finder window open, it’ll return the path of the frontmost one, else it’ll return the path to the home directory

try
	tell application "Finder" to set dirPath to (POSIX path of (folder of the front window as alias))
on error
	set dirPath to (POSIX path of (path to home folder))
end try

return dirPath

Update.

Solves issues with filenames that have special characters.

since such a specific app is not available for mac.

Not sure what you mean by that, there are a bunch of them, both CLI and GUI. Some are even featured on known websites.

btw, it sometimes takes time to show results and default callbacks are listed while it's searching, so just wait for the results. i did not look for the reason in specific, i m sure it s documented somewhere.

When using a Script Filter, Alfred reruns your command with every character entered/removed/changed. Since it’s trying to output something (by reading the results XML over and over), it may be something there — some operation your workflow runs where it doesn’t output the correct code (or any at all), that confuses it in that moment.

Updated to address some oddities.

Odd. I have no idea why that happens. Thank you for figuring it out, though, I’ve update the workflow to reflect that change.

There’s actually a workflow for that.

That really is weird, being touch such a basic command. Could you please redownload and install the workflow, just so we’re sure it’s really the latest version? There were some recently that kind of broke some things.

The download link is wrong (linking to a blank workflow).

It is possible, yes (link available for 30 days), but not without its flaws. The issue is that since we don't know when the page finishes loading, it may do it after ⌘+f was pressed, which will hide the find box (although you can press the shortcut again, and it should reappear with your query).

Change the url on first line of the Run Script to the one you want, and play with the delay amount on the second line, until you get something that works/is acceptable for you, your connection speed, and the website (until it seems to work fine with your specific case, basically).

It’s a bit of a hack, since it relies on waiting times and sending key presses, but it should work.

It should be, even if we use a bit of a hack to tell it to send the ⌘+f keystrokes. What is the browser you’ll be using, and is the url in question always the same?

Great workflow. Would be very useful to me. But unfortunately I can't seem to get this to work on OSX Mavericks. Anything idea?

One of the biggest challenges to make this workflow and its “sibling” work is that Alfred does not read your PATH and other things that your terminal does when starting. Different users also have different shells and configurations, which makes it harder to set this up in a way that works for everybody. This last update addresses those issues, in some form.

Can you please tell me what is your default shell (bash, zsh, other), where it’s located (are you using /usr/bin/zsh/, or /usr/local/bin/zsh, for example), what command you’re trying to run that fails, and how did you install it (is it a system command, or did you get it from homebrew or some other means)? Basically, the more details, the better.

Update.

More efficient way to run commands, and support for more shells.

Update.

More efficient way to run commands, and support for more shells.

When reporting issues, please include your exact installed versions of:

• The Workflow.
• Alfred.
• macOS.
  

In addition to:

• The debugger output. Perform the failing action, click “Copy” on the top right and paste it here.
• Details on what you did, what happened, and what you expected to happen. A short video of the steps with the debugger open may help to find the problem faster.
  

Thank you. Accurate and thorough information is crucial for a proper diagnosis which allows me to help you better.

But I'm not sure this is possible in Chrome due to their lack of applescript support.

What makes you think that? Its applescript support is pretty acceptable, and nothing to scoff at. It’s a lot better than a big percentage of apps out there, and certainly better than the majority of browsers, which range from having none to ridiculously deficient applescript support.

It’s a genuine question, though, what makes you feel its applescript support is poor?

Update.

It goes back to using bash, instead of zsh (a small remnant of previous tests).

Update.

It goes back to using bash, instead of zsh (a small remnant of previous tests).

Usage

Prevent macOS from sleeping via the coffee keyword. Optionally give a number when enabling to activate it for that amount of minutes, or hours if an h is appended. Action with ⌘↩ to also prevent the display from sleeping.

⤓ Install on the Alfred Gallery | Source

link doesn't work btw.

Not sure what’s wrong, I just tried it again and it worked.

You can make it even shorter and simpler. By adding a Copy to Clipboard node, you can relinquish pbcopy, and have the workflow automatically paste the text to the frontmost app. Something like this.

Keyboard Maestro lets you “launch macros directly by name” (on the video, they press ⌘⌥^T).

Update.

With this new version, youtube-dl will auto-update, if it's more than 15 days old.

Long due update.

It now saves a file, and then executes it, solving some issues.