Skip to content

ghc-mod / stack / dist dir #801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alanz opened this issue Aug 6, 2015 · 7 comments
Closed

ghc-mod / stack / dist dir #801

alanz opened this issue Aug 6, 2015 · 7 comments

Comments

@alanz
Copy link
Contributor

alanz commented Aug 6, 2015

I use inf-haskell-mode with GHC 7.10.2 and ghc-mod compiled from https://github.com/alanz/ghc-mod/tree/HaRe (basically ghc-mod master but exposing some more internals)

haskell-mode is set up out of the box from spacemacs

I have found that the on the fly checking goes into a continuous cabal configure reload loop as I type unless I make sure that the ./dist directory exists, either by doing cabal configure separately from stack, or by symlinking the output of stack path --dist-dir to ./dist.

@gracjan
Copy link
Contributor

gracjan commented Aug 7, 2015

@DanielG, @kazu-yamamoto: pinging so that you know there is a potential issue.

@DanielG
Copy link

DanielG commented Aug 9, 2015

I'm not familiar with inf-haskell-mode does that even invoke cabal configure somehow?

@alanz
Copy link
Contributor Author

alanz commented Aug 9, 2015

I think it is the ghc-mod using cabal-helper to read its cache, not finding
a dist-dir and doing a configure, which configures in the
.stack-work directory and so is not seen. And then this just repeats.

On Sun, Aug 9, 2015 at 2:29 PM, Daniel Gröber [email protected]
wrote:

I'm not familiar with inf-haskell-mode does that even invoke cabal
configure somehow?


Reply to this email directly or view it on GitHub
#801 (comment)
.

@DanielG
Copy link

DanielG commented Aug 9, 2015

Oh well that makes sense. But ghc-mod shouldn't go into a loop by itself. Something needs to be invoking it over and over.

@alanz
Copy link
Contributor Author

alanz commented Aug 9, 2015

That is the haskell-mode tie-in. The "loop" is triggered every time the
file is saved, when ghc-mod check is invoked on it.

On Sun, Aug 9, 2015 at 2:40 PM, Daniel Gröber [email protected]
wrote:

Oh well that makes sense. But ghc-mod shouldn't go into a loop by itself.
Something needs to be invoking it over and over.


Reply to this email directly or view it on GitHub
#801 (comment)
.

@DanielG
Copy link

DanielG commented Aug 9, 2015

So what happens when you do it on the command line?

@gracjan
Copy link
Contributor

gracjan commented Jan 27, 2016

As I understand ghc-mod supports .stack these days, doesn't it?

If there is something to do on haskell-mode then write here and we will reopen this issue.

@gracjan gracjan closed this as completed Jan 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants