Closed dnadales closed 6 years ago
Yes, after digging around for a bit I realized that flycheck
does not have a handle to point stack
to a custom stack.yaml file. I'll add that to the flycheck
project.
In the meantime you can take advantage of the following workaround: define STACK_YAML
environment variable to point to your stack_linux.yaml
file before invoking your emacs. This will affect all calls to stack within emacs though, so you'll likely will not be able to work on other haskell projects using this emacs instance (that depends, actually, on how dissimilar other project's stack yamls will be from stack_linux.yaml
you'll point to).
Thanks @sergv! My case is a pathological one, since most project use the default stack file, so I guess I can use the workaround you mention for the time being.
flycheck-haskell
work greats on all but one of my Haskell projects. The problem is that I have twostack
configuration files:stack_linux.yaml
)So each stack command I run on Linux for this particular project must include the flags
I don't know if there is a way of customizing this (I could not find it), but if not it'd be useful to have it in these circumstances.