Mesabloo

Inspecting the source code at the given position (in the error): https://github.com/phuhl/linux_notification_center/blob/a155a6b826b6380f9c712aa07e345a66d0b622a1/src/NotificationCenter/Notifications/NotificationPopup.hs#L129-L158 You can see that there is an edge-case (I think) where `valid` is `True` (so the mouse button...

One of the major setbacks would be the need to expose the internal definitions of e.g. reports, diagnostics, etc. (mainly all that is present in `X.Internal` modules which isn't exported...

I can take a look at how to structure that (and the best way to do it, although I may have an idea already) and maybe start working on it...

Alright so there's basically nothing we can do regarding the Unicode + Windows combination, other than proposing alternative ASCII layouts (which is already the case for the default layout, although...

I absolutely hate the fact that everything is misaligned, and it looks like Windows is trying its best to render the unicode box characters but absolutely fails to do so...

This shouldn't be a problem at all if your version of `hpack` managed to work correctly. :)

I started refactoring and moving code as per the first part of my first suggestion, in the branch [`custom-layouts`](https://github.com/Mesabloo/diagnose/tree/custom-layouts). For now, this is a simple move of the code which...

> I have just submitted https://github.com/solidsnack/wcwidth/pull/6, but I am not very positive that `wcwidth` will be updated soon on Hackage. Given that the code there is just a bunch of...

In the meantime, I went ahead and implemented a GCC-style layout (and style) for the library. Currently, this looks like this (this uses the same error as the one from...

> I guess similar things happen in `codespan-reporting` style, too. Though of course most annotations should be reusable, so after I finish debugging my implementation I should probably come up...