--allow-eval: ghcid doesn't start up when project has compile error

[mklinik]

If you have a compile error in your project, ghcid usually just starts up and shows you the error. But with --allow-eval enabled, it terminates with the following error message:

ghcid: /home/mkl/sandbox/haskell-misc/hello-world/<unknown>: openFile: does not exist (No such file or directory)

If you start ghcid with --allow-eval in an error-free project and then add a compile error, ghcid works as expected.

How to reproduce:

• add --allow-eval to .ghcid
• have a project with compile error
• start ghcid

[ndmitchell]

Thanks for the bug report. I don't actually use --allow-eval ever, so I'm unlikely to ever investigate in any depth. You're welcome to take a look, and I'd certainly accept a patch. Alternatively, maybe @akrmn or @isovector are interested in taking a look (as previous contributors of --allow-eval stuff)