Closed PierreR closed 10 years ago
The docset path bug strikes again, and at the very least my activate-package-docsets
may be taking too many packages. Are you using the latest helm-dash?
Yep the latest version from github (acee4e4b31af5326fb147bdc673b5e51b9aa4c20) . I have been using dash-docklet
from the root of a cabal sandbox project. The generated docklet folders looks ok. But the output of activate-package-docsets
seems wrong. For instance, aeson-0
instead of aeson-0.7.0.6
?
Understood. I patched a fix for a similar bug in helm-dash recently: https://github.com/areina/helm-dash/pull/57 I'm aiming to complete a fix for this as well, along with a fix to stop the function from union'ing packages, this weekend.
I have just tried your patch by manually installing the master version of helm-dash
. It works ! Thanks for the tip (and the patch ;-)
activate-package-docsets updated with d16fb637c6b7f734c468a058ca7bd069eb9948f0
From the README:
Unfortunately it does not seem to work for me as it creates :
While the docsets dir looks like this
Thanks for your help.