Closed michaelmesser closed 7 years ago
1) You may want to run stack build
from command line when changing dependencies or stack.yaml. That's a bit awkward, I know.
2) ghcjs isn't really supported by ghc-mod (yet). So...
3) Is your stack.yaml even configured to use ghcjs? https://docs.haskellstack.org/en/stable/ghcjs/
@lierdakil I am using GHCJS-DOM with GHC not GHCJS. I ran stack build which worked fine. I do not need this to work anymore since the dependency is on hackage now. I ran ghc-mod by hand on the files and it worked fine.
I am using GHCJS-DOM with GHC not GHCJS
Ah, ok. Sorry for my assumption.
Well, long story short, hgm runs several ghc-mod processes to increase overall responsiveness -- and it works fine on multi-core systems most of the time. However, there are some cases when it fails -- usually when ghc-mod decides to run stack build
-- which is usually when there are dependencies missing. There's a fix in the works currently, but it will be some time before that's released (ghc-mod is the blocker here).
Hgm's setting 'Low Memory System' forces single-threaded operation, which can help with this problem somewhat, but at the cost of considerably longer initialization times.
I'm going to close this for now, since there's a relevant issue open already.
One of the directories in .stack-work/downloaded and deleted and recreated very quickly. Running ghc-mod from the command line works fine. This issue only occurred after I added a dependency to stack that in downloaded directly from github.
[Enter steps to reproduce below:]
Atom Version: 1.11.1 Electron Version: 0.37.8 System: Mac OS X 10.12 Thrown From: haskell-ghc-mod package, v1.18.0
Stack Trace
Haskell-ghc-mod: ghc-mod command check failed with error Error
Commands
Config
Installed Packages