You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Thanks for letting me know. I'll add a note to the README mentioning it for future shortcuts added, or the updating of old one where other are having this issue.
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, callingdash://ruby:{query}
will no longer work. However, callingdash-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.
The text was updated successfully, but these errors were encountered: