Closed dubreuia closed 5 years ago
Hi,
I haven't used Stack but if you have to call stack ghci
to run ghci then, yes, you have to change the way ghci is called in bin/tidal
. You can also write export GHCI=stack ghci
at the end of your .bashrc
or .profile
without changing the bin/tidal
script, because it uses that environment variable by default.
Another thing you could try out is not using Stack at all, and install Tidal with Cabal, which is the official package manager (I believe at the time of writing of the Tidal tutorial, Stack was the preferred way, but I haven't had any issues with Cabal recently). You should run:
cabal update
cabal install tidal
Ok thanks I'll look into cabal
this evening and close this issue if it works.
Hi,
I'm following this guide "https://tidalcycles.org/getting_started.html" for linux (ubuntu 17.10).
I have the same problem than #16, but I don't know how to fix it. "This plugin works only with Tidal 0.9+, and it looks like you have 0.8 installed right now...". How do I test that? How do I upgrade?
Something looks wrong in my installation:
I think tidal is installed in stack (I installed it using
stack install tidal
but not inghcl
). I have no idea what I'm doing by the way.So I modified the tidal launcher in "bin/tidal" with
And it works. It also works with no modification in Atom with the tidalcycles plugin.
Thanks
EDIT I also have a warning I don't understand "Warning: No local targets specified, so ghci will not use any options from your package.yaml / *.cabal files."