Tyler Eich

Alfred pays attention to Spotlight comments, so adding "lr" and "ps" to the Spotlight comments of Lightroom and Photoshop is another solution

Why is there a <snip> tag in the middle of your XML?

You could use the color scheme to generate an Alfred theme URL. For an example of what format to use, go into Alfred Preferences > Appearance, choose the theme you'd like to base the rest on, hit the "Share" button at the bottom, and choose "Copy Theme URL". Paste it somewhere and you'll have a pretty good idea of how to generate a theme URL

I believe it's a data representation used by Objective-C in plist files. I'm not aware of any way to parse the color data (except to load the color data back into an Objective-C program) You could use the NSColor class to convert eg RGB to a native color representation, which should be able to be written to the plist. And of course, manipulating Alfred's hidden files directly is highly discouraged, as Alfred's stability depends in part on the integrity of these files.

I'm sure it's possible, but I don't think it's under consideration right now… I'm guessing that using a permanent (i.e. not cached) image in Alfred's interface would consume more memory. I know Andrew works feverishly to keep Alfred lightweight

I'll probably post the source code on GitHub at some point. Here's a quick look in the meantime: http://cl.ly/code/3a402k0D1s2v By the way, I'm not actually extending the codebase for Alfred's calculator. The workflow feels like an extension of the calculator because it is triggered by the same characters that trigger the normal calculator (i.e. 0-9 and +-). These keywords act as a bridge to the binary, which returns results very similar to Alfred's normal calculator. It's also very fast, mainly because it's written in C.

I made a workflow to do this Check it out: http://www.alfredforum.com/topic/4568-duration-calculator-%E2%80%94-add-and-subtract-durations-of-time/

This workflow extends Alfred's built-in calculator function. It recognizes durations as input and allows them to be added / subtracted. For example, if you type "8:00:18 - 4:19:23" into Alfred, you'll get "3:40:55". You may add or subtract as many durations as you like (e.g. "3:32:55 - 5:57 + 4:50:14"). Download Preview:

If you use the 'Terminal Command' action, Alfred will open a session in Terminal.app (or whatever Terminal emulator you've selected in Alfred's preferences) and run the specified command. The session will be interactive, allowing the user to provide input.

I found two apparent issues (PHP is not one of them): You are calling htmlentities twice on the same piece of text. The first run produces "&é", which is valid. The second run re-encodes the ampersands and corrupts the output. Your XML is missing the <?xml version="1.0" encoding="UTF-8"?> header. I'm not sure if that's part of the issue. Hope this helps!

If you have a Powerpack License, you can create a workflow with a hotkey to capture the current selection. Set the hotkey's 'Argument' to 'Selection in OS X'. Then connect the hotkey to whatever action you want to process the text with. Alternatively, you can tell set the hotkey's 'Action' to 'Show Alfred'.

After reading about your dilemma, I realized that I face the same issue on a daily basis. So I made a workflow that should cover our needs Download You can type 'sheet' and search for the file, or you can use the 'Send to Sheet' file action. When you send a file through this workflow, it will attempt to interact with the frontmost sheet. It will tell the sheet to load the folder provided, or the parent folder if a file is provided.

I want fallback results that link to any input object. If the script filter were automagically called when nothing else matched, I might mistake it for normal results. If, however, there was a fallback option which connected to a script filter, it would still be clear that the choices are fallback results. Here's a mockup to explain what I mean: Mind that the connection between a Fallback Search and a Script Filter is not possible; if the above feature was added, it would be possible.

To answer your first question: yes, any time you enter a query into Alfred, every keyword that matches that query will be run and added to Alfred's results. This is by design. To answer your second question: there's no way to get Alfred to use a script filter as a fallback search with instant results. One way to work around this is to add a hotkey to the workflow and connect it to the keyword you want for search. When you press this hotkey, Alfred will open and provide results from the connected keyword. So rather than hitting your default Alfred hotkey and getting Chrome results in the default results, you'll press the special hotkey to search only Chrome bookmarks and history

Have you tried creating a new user account and installing Alfred there? Do you have the same issue?

I agree. It's a very minor detail, but would facilitate workflow creation

Any existing functionality mentioned here requires you to have a Powerpack license: The clipboard snippet feature does have its own hotkey. By default, it's Option + Command + C, which searches only Clipboard Snippets and History I'd venture to guess that, in the future, adding snippets will be very accessible, including the clipboard history contents and selected text options. Andrew doesn't ignore user feedback Using hotkeys, you can perform actions on both selected text and files. Not sure about OS X Services integration, but that would be a cool functionality; perhaps a workflow will eventually crop up allowing this kind of integration

This is possible without a workflow. Type 'C' into the search bar at the top left of the Workflows section of the Alfred Preferences. It will search hotkeys along with other fields like "Name" and "Creator"

The following suggestions require a Powerpack license You may be interested in one of two workflows by deanishe: Subdirectory Search Fuzzy Folders (deprecated Subdirectory Search) Or you could create a custom file filter that only searches the 'mysite.dev' folder you mentioned. With this method, you'd have to add a filter for each folder where you wanted to isolate search.

You're absolutely right! Alfred uses OS X's Spotlight data, which doesn't include these folders. Bummer

It would be best for you to just bring the 'define' keyword to the top. To do this, simply type 'def' and choose the 'Define' option. After doing this a few times, Alfred will remember that you use 'def' to access 'define' and will put it at the top.

I'm assuming you're using a Script Filter. I can think of several ways to do this, but the method I think would be best is as follows: In your code, save a .txt file (in the workflow's cache directory) for each word result. Add type="file" to each <item>. Set the arg attribute to the path to the respective file saved in the cache directory. Why? This will allow you to add the results to the file buffer. By default, ⌥↑ or ⌥↓ will add files to the buffer. Add a Run Script object between your Script Filter and Copy to Clipboard object. Set this Run Script object to read every path in {query} (remember they're separated by tabs), concatenate the text together, and output the text. Add a File Action object that accepts multiple .txt files. Connect it to the Run Script object from the previous step. Why? If you only want one definition, you can just hit enter, which will read the text from the single file (specified in the argument of the result you chose) and spit it out. If you want multiple definitions, you can add the appropriate results to the file buffer, hit ⌥→ (opens the action panel), and choose the File Action specified earlier. This will cause the script to read each file, concatenate the results, and spit out one string for copying. This description may be a little abstract without an actual workflow. If you want an example of what I've described, let me know and I'll see what I can whip up

Thanks for the notice! Try downloading again; I've updated the workflow to v1.1.1 to fix this issue

I've updated the workflow to version 1.1, which handles this error. Thanks for the report! I've also started a separate thread for any new issues that may arise

This is a very simple workflow that displays and sets Alfred's background blur radius. Obviously, you'll only see its effects when running a version of Alfred that supports the background blur (namely, Alfred 2.0+ on OS X 10.6 through 10.8, Alfred 2.3+ on OS X 10.9). Enjoy! Download from Packal