You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been reading through issues like #809 discussing the ghc-mod / haskell-mode relationship.
Initially, when using modern haskell-mode, I was very surprised that my errors came up in my REPL when evaluating the buffer, but that they weren't highlighted in the source. In fact, as of current HEAD (d11f7b2), pressing enter on the message in the REPL kindly highlights and switches to the error, which is great.
But it sure would be nice for that to happen eagerly rather than lazily, via switching buffers and clicking on each error. Indeed, being able to see error messages before even taking eyes off the code is such an addictive aspect of using ghc-mod. And it would be great to have that even with just haskell-mode.
I haven't found any docs that address this, so I think it would be nice if there's one place that contains the answer to this question. That is -- is it hard or non-sensible for some reason to go back and paint the relevant buffers with highlights at the point all these error messages are discovered?
The text was updated successfully, but these errors were encountered:
I've been reading through issues like #809 discussing the ghc-mod / haskell-mode relationship.
Initially, when using modern haskell-mode, I was very surprised that my errors came up in my REPL when evaluating the buffer, but that they weren't highlighted in the source. In fact, as of current HEAD (d11f7b2), pressing enter on the message in the REPL kindly highlights and switches to the error, which is great.
But it sure would be nice for that to happen eagerly rather than lazily, via switching buffers and clicking on each error. Indeed, being able to see error messages before even taking eyes off the code is such an addictive aspect of using ghc-mod. And it would be great to have that even with just haskell-mode.
I haven't found any docs that address this, so I think it would be nice if there's one place that contains the answer to this question. That is -- is it hard or non-sensible for some reason to go back and paint the relevant buffers with highlights at the point all these error messages are discovered?
The text was updated successfully, but these errors were encountered: