Open reactormonk opened 4 years ago
Did you specify a specific -c
flag to ghcid to control the command? If not, what command did it pick? (It should say on the first line). I suspect this information will be of interest to anyone upstream, but a quick look at it might tell me if ghcid is doing something wrong. Alternatively, is there any -c
command that works? If not, that's definitely an upstream issue.
I went via -c cabal new-repl <subproject>
. What works is stack repl <subproject>
, so I didn't investigate further.
Sounds like an issue for cabal
then.
The error paths are relative to the subproject root, which messes up the vscode integration. The problem only exists with cabal - stack uses absolute paths when reporting errors. Should I kick this bug upstream?