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

Missing "extra-source-files" causes breakage #13

runeksvendsen opened this Issue Nov 3, 2018 · 3 comments


None yet
2 participants

runeksvendsen commented Nov 3, 2018

  • Version of vscode-ghc-simple: 0.0.10
  • Version of VSCode: 1.28.2
  • Version of Haskell-related tools:
    • GHC: 8.4.3
    • Stack: 1.8.0
    • Cabal:

Steps to reproduce

  1. Add file to the "extra-source-files" section of .cabal/package.yaml that doesn't exist
  2. Start VS Code

The following is printed to the VS Code "OUTPUT" console:

ghci | The following errors occurred while parsing the build targets:
ghci | - Unknown local package: Warning

This comment has been minimized.


dramforever commented Nov 4, 2018

This seems like an error from stack. Can you check the output of stack ide targets? Also, can you start stack repl properly?

It seems that all the hacks used to get the repl working is bound to keep breaking. I'll have to learn how ghc-mod and others do this.


This comment has been minimized.

runeksvendsen commented Nov 4, 2018

stack ide targets gives the following output (to stderr):

[runesvendsen@mbp ~/code/crypto-depth-db (master *)]$ stack ide targets

Warning: Specified file "" for extra-source-files does not exist

stack repl seems to work just fine.

As far as I can see, stack shouldn't be mixing warnings with the actual output of the stack ide targets command. Warnings could be sent to stderr and the actual output to stdout, which would mean it'd be easy to filter off the unwanted output.


This comment has been minimized.


dramforever commented Nov 4, 2018

Ha! That makes so much sense. Thanks.

I've just replaced the hard drive on my laptop. I'll update when I get my things back in working order.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment