I want to add java support, but dashAlfredWorkflow command seem not support it.

Just to let you know, Dash 2 will improve the Alfred workflow by dynamically adding keywords for each docset the user has installed, as well as search profiles. So, if the user has the PHP docset installed he can type "php {query}" in Alfred.

It's basically the same thing as your workflow, except that only keywords the exist are added to the workflow.

Since upgrading to OSX 10.9, everytime I try to use Dash I get a "Couldn't load Dash" error message.

I'm using Alfred 2.1 (218).

Any ideas?

Is this project accepting new languages additions?

There's a huge list of these missing like:

• Bourbon
• Android
• Clojure
• CoffeeScript
• D3.js
• Django
• JQueryUI
• Elisp
• Python2
• Python3
• YUI

and more...

There's a total of 101 docsets and we're only covering 24.

Reported by @kpantic on zenorocha/alfred-workflows#20 and zenorocha/alfred-workflows#13

It simply doesn't seem to work. Versions:
OS X: 10.8.5
Alfred: 2.1 (218)
Dash: v1.11

Is there any interest in adding script filter for "iphoneos" ?

When trying use this workflow, every trigger shows the correct Title and placeholder when I type in the keyword, but immediately falls back to a Google search when I type anything after the space.

I believe the issue might be with my using an older version of Dash as I am running v 1.8.1 on OSX 10.6.8. I'm not sure if the ./dashAlfredWorkflow is actually pulling in an existing workflow or not.

Attached are relevant screenshots of the issue.

Thanks in advance!

After typing the keyword:

After typing a single letter after the keyword:

willfarrell/alfred-workflows#22

If I try to search for something that has a $ in it, no results are returned. For example, angularjs $rootScope.

Dash 1.9.3 comes with a new way for plugins to call Dash and send over a list of keywords which Dash uses to enable/disable docsets.

This is all described at http://kapeli.com/dash_plugins.

This was designed for IDEs and editors, so that they can activate more than one docset at a time based on the type of the file they're currently editing.

Even if you only want one docset at a time, I suggest that you change the workflow to also use the new URL scheme. The only benefit in doing this is that the workflow will still work if the user changes his keyword preferences.

So, for example, if the user sets r: as the keyword for Ruby, calling dash://ruby:{query} will no longer work. However, calling dash-plugin://keys=ruby&query={query} will still work.

One thing to look out for: you need to percent escape the {query}, otherwise things will fail when the user searches for things that cointain a & (and possibly other special chars as well).

As the benefit is not that huge, it's up to you whether or not to change things.

Hi,

Could you add support for Haskell?

Regards,
Rik

willfarrell/alfred-workflows#23