VS Code extension gets confused by --allow-eval

ndmitchell / ghcid

Very low feature GHCi based IDE

Other

1.13k stars 114 forks source link

VS Code extension gets confused by --allow-eval #326

Open anka-213 opened 4 years ago

anka-213 commented 4 years ago

If I put--allow-eval in a .ghcid file and run the VS Code extension (with the "Run Ghcid" command), it will report all of the evaluated output as problems in the file "/".

anka-213 commented 4 years ago

It's not a major issue, I could just run ghcid --allow-eval in a normal terminal inside vs-code instead.

ndmitchell commented 4 years ago

I don't really use the plugin much anymore (I've mostly moved on to Ghcide - https://github.com/digital-asset/ghcide), and I've never used --allow-eval. Happy to take a patch - it's probably a matter of adjusting a regex in the Javascript code - but unlikely to tackle it myself.