Using ghcide to try and debug problems is hard

[ndmitchell]

It used to be that if I ran ghcide in a directory I got a brief report of what worked, what didn't, and from that I could infer what to do.

Now it spits out thousands of lines of stuff about DEBUG/INFO, and I can't even find the information I want. That means I have no idea why my program doesn't work. In my case its filled up the terminal buffer so completely I am only left with reports from a directory I don't care about.

Worse than that, the final line tells me that all files apart from 1 worked. But in practice, none of my files are working in the IDE. Is that because they are working somehow differently to ghcide on the command line?

Should I be running some haskell-language-server operation to figure out whats going on?

[michaelpj]

I think this amounts to "make the logging better", which we already have some tickets for.