However, I do not like how it deals with matches in multiple docsets.
E.g. when you search for "String" and have the Ruby and RoR docsets enabled, then it will always show the RoR one first. The only way to switch to another one seems to be by clicking that microscopic icon in the list.
Possible fixes (ideally implement them all):
1. Optionally show all hits separately in the list (then I can just click directly on the Ruby or RoR version)
2. Display a toggle-bar at the bottom of the window where I can quickly enable/disable any docset. Most of the time I'll only want to search in one particular docset anyway.
3. Provide large buttons at the top of the right pane for each matched docset, to easily switch to a different version (Ruby, RoR, ...).
Other than that: Great work. If this issue gets fixed I could see this tool becoming part of my workflow (and paying for it).
Thanks for the enter-tip, that's helpful! (although I still don't like having to do it every time).
Yes, showing them separately seems like the easiest permanent fix. Ideally with the docset toggle-bar, so the noise can be cut down quickly when zero'ing in on one language for a few minutes (that's what typically happens in my workflow; digging into coffeescript for a while, then some ruby, then again coffee, etc.).
However, I do not like how it deals with matches in multiple docsets.
E.g. when you search for "String" and have the Ruby and RoR docsets enabled, then it will always show the RoR one first. The only way to switch to another one seems to be by clicking that microscopic icon in the list.
Possible fixes (ideally implement them all):
1. Optionally show all hits separately in the list (then I can just click directly on the Ruby or RoR version)
2. Display a toggle-bar at the bottom of the window where I can quickly enable/disable any docset. Most of the time I'll only want to search in one particular docset anyway.
3. Provide large buttons at the top of the right pane for each matched docset, to easily switch to a different version (Ruby, RoR, ...).
Other than that: Great work. If this issue gets fixed I could see this tool becoming part of my workflow (and paying for it).