Try harder to find dash installed docsets

[tko]

The paths where dash itself installs the docsets is somewhat
unpredictable (#84) and can not be reliably determined from the docset
name/id alone. For example:

• Bootstrap_2 => Bootstrap_2/Bootstrap.docset
• Bootstrap_3 => Bootstrap_3/Bootstrap 3.docset
• Emacs_Lisp => Emacs_Lisp/Emacs Lisp.docset

Try harder to find them simply by looking inside the directory and
accepting the first *.docset directory present. The list of paths
searched is now:

• {name/id}.docset -- helm-dash installation, probably
• {name/id}/{name/id}.docset -- dash installation, e.g. Haskell
• {name/id}/*.docset -- dash installation, e.g. Bootstrap_2

[areina]

Merging, thank you @tko !!

[rswgnu]

Downloaded the latest helm-dash today and having a problem like this with the Python_3 docset. All other docsets that I use appear in searches but nothing comes up for the Python_3 docset. I don't know yet if it is the underscore or the fact that many of its html and toc files are in subdirectories. Does helm-dash handle docsets with many subdirectories of HTML files?

[kidd]

My python3 docset looks like "Python 3" in the docsets list and works ok. Make sure helm-dash can find the docset in the path+name

[rswgnu]

Yes, the path is found and the docset is named Python_3. It was downloaded by the Windows Zeal docset application. All the other docsets in the same directory show search results in helm-dash as far as I can tell, except this one. If you want to see the output of some function call, just let me know. I tried to have helm-dash download its Python 3 docset but it just hung and never got to the downloading.