Fallback results in script filter

[gianx]

Hi,

 

when I write a script filter, the output is sometime mixed with fallback results.

 

For example I have a "Hue" workflow that outputs the name of the bulbs available in my network, but together with the name of the bulbs I get also "hue.py" (the script) and "How to hue...pdf" (a pdf).

 

How can I prevent that?

 

Thanks, Gianluca

[jdfwarrior]

Hi,

 

when I write a script filter, the output is sometime mixed with fallback results.

 

For example I have a "Hue" workflow that outputs the name of the bulbs available in my network, but together with the name of the bulbs I get also "hue.py" (the script) and "How to hue...pdf" (a pdf).

 

How can I prevent that?

 

Thanks, Gianluca

 

The easiest way would be to change the keyword that activates the workflow. From the sounds of it, you have Alfred configured to show everything in the default results. This has the tendency to make your results kind of cluttered which is why its disabled by default. It makes it easier to show everything by default but results are a lot cleaner and a lot more accurate if you limit default scope and have workflows setup to perform more specific searches. For instance, one that I use all the time is folder only results. I use , as a keyword to show only folder results when searching rather than having to search through a mass of results for everything that could match my query.

[deanishe]

Like David said, change your keyword and you're golden.

 

If your keyword matches default results (or other keywords), they'll be shown until you dive down into that specific workflow.

 

Because I prefer short keywords, I tend to prefix them with ".", e.g. ".st" or ".sf" (and in your case, ".hue"). Using a period/full stop is particularly effective, as Spotlight (and therefore Alfred) doesn't index any files beginning with a period/full stop (they're hidden files).