Show example of use in autocomplete

[ndr-brt]

Maybe we can take informations from haddock docs:
http://hackage.haskell.org/package/tidal-1.4.3/docs/

or from the wiki:
https://tidalcycles.org/index.php

[yaxu]

The 'hoogle' library is probably a good interface for retrieving haddock
It can integrate with ghci

[ndr-brt]

way better, so it will work also offline

[ndr-brt]

@yaxu I'm trying to get docs from hoogle but maybe I'm missing someting...
I'm playing with it from cli
with hoogle -i "tidal"
it prints:

package tidal
Not on Stackage, so not searched.
Pattern language for improvised music

but I'm not able to get a single function docs. e.g. both:
hoogle -i "tidal.Sound.Tidal.UI.rand"
hoogle -i "Sound.Tidal.UI.rand"
don't work

obviously, with:
hoogle -i "rand"
it gives me the docs of the basic rand function.

[ndr-brt]

I think the problem is that:
Not on Stackage, so not searched.

Hoogle from version 5 is based on stackage.org database, according to hoogle README, and Tidal is not on www.stackage.org

I saw some issues on tidal repository about stackage:
tidalcycles/Tidal#73
tidalcycles/Tidal#405

[yaxu]

It is in the nightly build: https://www.stackage.org/package/tidal I don't know why it hasn't made the LTS release that came out four days ago.

…

On Thu, 31 Oct 2019 at 12:11, ndr_brt ***@***.***> wrote: I think the problem is that: Not on Stackage, so not searched. Hoogle from version 5 is based on stackage.org database, according to hoogle README <https://github.com/ndmitchell/hoogle/>, and Tidal is not on stackage.org I saw some issues on tidal repository about stackage: tidalcycles/Tidal#73 <tidalcycles/Tidal#73> tidalcycles/Tidal#405 <tidalcycles/Tidal#405> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#64>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAG2JBVDX2QV4UV5YEU2STQRLDOVANCNFSM4JETQGUA> .

-- blog: http://slab.org/

[ndr-brt]

ok...
I made it working in local running:
hoogle generate tidal.

But there's a lot of blind spots... Maybe would be better to add a hoogle path configuration, to specify if it's installed as binary or used with stack, more pratical than integrating it with ghci.