Olaf

Thanks vitor,

I am now using a "Run NSAppleScript" workflow command with the following content and it works fine:

on alfred_script(q)
  tell application "System Events"
    keystroke "q" using {control down, command down}
  end tell
end alfred_script

It would be great if you could still supply the link to the workaround script here for people still using Alfred 2 (like myself).

I see, thanks for the update!

We've added a note to exclude Audiobooks as well in the next update.

Cool, thanks!

I am also missing the feature to exclude all media that is in the iTunes "Audiobooks" section fom Alfred's mini player.

Thanks Andrew, I deleted and rebuild the OS X metadata but it did not help.

However, I found a much simpler demonstration of what appears to be the problem:

As stated above, I have a workflow with a File FIlter that I can trigger by the keyword "bo".

Now, if I search for something like this:

 "bo e e e e e e e"

it should be the same as searching for

 "bo e"

BUT: If I type

 "bo e e e " (please note the final space at the end)

then the result depends on my typing speed: if I pause a bit after the last "e" before typing the final space, the result always looks good, but if the last "e" is quickly followed by the space, the result is empty.

I can easily reproduce this, but I suspect that you may need a few of files in the search scope to trigger this.

Hi,

I have an issue with a simple File Filter workflow:

The workflow in question is just a File Filter attached to an Open File action.

I trigger the File Filter search by a keyword "bo", then I type in two search terms ("x", "y"):

 bo x y

If I do this at an even moderate speed, the search result is often empty. However, if I backspace up to right after the "x", then again type "<space>y", the result comes up just fine. The faster I type, the more likely the result is empty. The shorter the search terms (= the more matches), the more likely the result is empty.

The File Filter uses the following options:

Basic Setup:

 - with space: off

 - file types: 5 types, com.adobe.pdf, com.lizardtech.djvu, dyn.ah...cre,

    dyn.ah...dr (Amazon files), org.idpf.epub-container

Search Scope:

 - 4 folders in my home dir

Advanced:

 - date range: any date

 - fields:

   kMDitemDisplayName [ ] {query} [x] [x]

   kMDitemFinderComment  [ ] {query} [x] [x]

- accuracy [x] Anchor searches which are not word based

I am running OSX 10.8.5 with Alfred 2.1.1

Thanks for looking into this!

Olaf

Just make two of them. Different keywords, different outcomes, sounds like a separate script to me.

Sure, that would be possible, but it would mean to duplicate code: in the example above, suppose you want to do a some processing on the items, regradless of the destination being "home" or "work".

Hi,

I can not find a way to access the actual keyword entered if a workflow is triggered by a keyword input. I can only get the arguments via {query}.

Getting the argument would allow to handle multiple keyword commands in a single script.

For a simple example, suppose I want to process and then add items to either a "work" and "home" folder. Currently, unless I want to duplicate my script, I can use a single keywork "add" and the must specify the destination as the first argument, for example:

 "add h item1 item2" (to add items to "home" folder)

 "add w item1 item2! (to add items to "work" folder)

But if it was possible to access the keyword from a query I could use

 "addh item1 item2" (to add items to "home" folder)

 "addw item1 item2! (to add items to "work" folder)

Any throught or ideas?

Cheers,

 Olaf

Hi,

most of the more sophisticated workflows rely on additional scripts in the workflow folder, which is not always obvious.

Therefore, I would like to suggest to add a row of icons to the buttom of the workflow edit pane, listing all the additional files found in the workflow folder and allowing to open these files from there.

I am aware that there is already a button in some of the workflow actions to open the workflow folder in the Finder, as well as a context menu item for that.

Cheers,

 Olaf