deanishe

So that's Alfred removing the Script Filter output? I did wonder how you were getting an arg out of a Script Filter with no items…

Awesome! If I had one wish for the debugger, it would be a "show everything but the JSON" option. It's important to be able to see the JSON when you need to, but if that's not what you're interested in, the sheer volume of output from some Script Filters overwhelms the rest.

Pipes work fine. Any script output to STDOUT will be passed as input to any downstream Post Notification output. You're probably doing something wrong, like printing an empty line that's causing your actual message to disappear.

I was trying to figure out where the trailing whitespace in my Script Filter query was being stripped (Alfred, my library, the CLI-argument-handling library). I hadn't realised that Alfred only logs output (seeing as Script Filters are about the only element that don't necessarily accept the output of another element). It would be helpful if Alfred also logged the input to elements that aren't consuming the output of other elements, especially now Alfred has different modes for handling whitespace in input. Not that it's a particular chore to add echo "query='$1'" >&2 manually. (In this case, I'd failed to fully recompile the program after removing my own trim command.)

No, that's how version 1 worked.

It's almost impossible to say with so little information. Please provide a detailed description of your problem, otherwise it's unlikely that anyone can help you.

Don't know. Certainly, you don't need to with HFS-formatted drives, but I don't know much about NTFS-formatted ones. In any case, macOS does have a habit of indexing non-native volumes differently.

Alfred v3.4 [843] Selecting "All information" in the debugger doesn't show the input passed to Script Filters.

If you try to change the network settings via a script, macOS will require your password. It's a basic security feature. If you don't want to be asked for your password, you need to create a privileged helper program, which will require you to enter your password to install it. It might also be possible to enable your script to work by editing the sudoers file.

Nope, sorry. The iTunes script works for me.

Don't use Run NSAppleScript. Use a normal Run Script action instead, with Language set to /usr/bin/osascript (AS).

https://discussions.apple.com/thread/3236464?start=0&tstart=0

Yeah. In the first version mailto was the keyword for sending. And then I realised that it should be @.

In that case, it works.

It doesn't hang, but it also doesn't work as it should. It's now working the same as my NSTask test: it opens a temp file with the data read from STDIN (i.e. an empty file). It should only activate the Sublime Text application.

Nope. The workflow has an out-of-date version of a library that doesn't get along with Sierra. That is almost certainly what was preventing you from selecting Airmail. Here's the solution. Run that workflow and it will fix MailTo and any other workflows you have that are affected by the bug.

Because the downloader it integrates with doesn't support fetching audio instead of video. I already have browser bookmarks and Pinboard for saving URLs for later (both of which sync to my other devices), and an unwatched tag for files. Instead, I save the URLs to Pinboard with a download-audio tag, and pipe my bookmarks through jq to youtube-dl.

I can't do anything with a screenshot. Please post an actionable description of your issue. Open Alfred's debugger (to turn on debug mode), run Force Reload from MailTo's settings screen (keyword mailto), then open the log file with mailto workflow:openlog and post the log messages from the update_apps.py script.

Nope. Node projects are basically Alfred's kryptonite, due to the lack of a useful blacklisting feature in Alfred and the absolutely insane number of files npm dumps in a non-hidden directory within your project folder (a small Vue.js project I'm working on contains 205 files called readme.md!) If you want to use Alfred's native search with node projects, your only real option is to add each and every one of your node_modules folders to Spotlight's Privacy pane in System Preferences. If you use git with your projects, you might find this workflow better than Alfred's built-in search, as it's tuned for working with git repos. If not, your best bet is to write a simple Script Filter that only returns directories that are immediate children of ~/Code.

Screenshots are not enough to diagnose issues. Please open Alfred's debugger, run vpn workflow:update, and post the debug output.

It finds Airmail 3 just fine. Do you still have Airmail 2 installed? If so, you need to uninstall it. If you have multiple applications with the same bundle ID, the system will only recognise one of them.

On a related note, the first line in Clipboard and Snippets in the changelog for build 837 reads:

Alfred MPD Control MPD from Alfred. Installation Download the latest version from GitHub releases or Packal. Usage mpd [<query>] — View mpd status and search for tracks On actions: ↩ or ⌘+<NUM> — Perform action On tracks: ↩ or ⌘+<NUM> — Queue track ⌘+↩ — Play track ⌥+↩ — Clear queue and play track ^+↩ — Queue album On albums/artists/playlists/types: ↩, ⇥ or ⌘+<NUM> — Search within albums/artists/playlists/types Licencing, thanks This workflow is released under the MIT licence. It is based on the Alfred-Workflow library, which is also released under the MIT licence. Changelog 0.1.0 First release

Handy. I found a bug and have a couple of suggestions. It doesn't work if there are spaces in the filepath, as some of the variables/arguments in the script aren't quoted. FYI, Alfred removes keyboard shortcuts when a user installs a workflow, so it doesn't work "out of the box". The user has to set their own keyboard shortcut first. Have you thought about adding a File Action as an alternate way to run the workflow? That way, you can use it from Alfred's file browsing mode, and it's also helpful for old people like me who can't remember all their keyboard shortcuts. Also, I think I found a bug in the bash script: Isn't there an "echo" missing here?