Daniel Gröber (dxld)

This is more or less intended behavior, the project detection is based on the CWD, not the path you pass in for the simple reason that not all commands have...

As for a workaround, how about: ``` #!/bin/sh cd "$(cd $(dirname "$1"); ghc-mod root)" ghc-mod check "$@" ``` but that of course only works for check.

Have you tried comparing the memory footprint when you load Futhark in `cabal repl` or ghci vs ghc-mod? If that's about the same then you ought to report this with...

I tried to reproduce this under windows but couldn't get it working with either stack or cabal because of a really strange build failure in futhark. First time I compile...

I think this is the same issue as https://github.com/DanielG/ghc-mod/issues/432, never got around to fixing that unfortunately.

Same thing as here probably: https://github.com/kazu-yamamoto/ghc-mod/issues/605

I'll properly think about this tomorrow I'm at home now :P

Can you try removing `.stack-work/dist/*/Cabal-*/setu-config.ghc-mod.*` those are our persistent caches that might be getting in the way again and not being invalidated properly. If that doesn't help then this sounds...

My guess is it has to do with this being a superproject since we didn't actually test that I think. I don't have time to debug this myself but if...

I think I need a test case to debug this in any meaningful way, so if anyone wants to construct an simple project that exhibits this problem or just link...