Multiline spans look weird about diagnose HOT 6 CLOSED

@mateiadrielrafael I managed to reproduce your error completely, with the new enhancements from your suggestions.
This looks like this:

All the bugs should have been fixed, and your suggestions have also been implemented : there is now a vertical ellipsis when line numbers are not consecutive -- I am quite unsure if this fits well or not --, and multiline markers are output at the end of the line they stop on.

I think this looks way better now, thanks to your suggestions!

from diagnose.

The fixes have been published in the version 1.8.2.
Thanks again for the report and the cool suggestions!

from diagnose.

Thanks for the report!

The non-connection issue may be caused by a behavior I did actually not think about, where a multiline marker does not end at the last line of the report.
This may be mitigated by your suggestion number 2, which, now that I think about it, is far better than the current design.
I also like your suggestion of putting ⋮ (with an empty line) when multiple ranges of code are not next to each other in the same report.

The issue 1 is however most probably a case I did not handled when coloring source code (when a multiline marker goes over the entire line without beginning/ending on it).
This should be a simple fix, I think. (inline markers need to be prioritized over multiline markers though)

from diagnose.

That's super cool! Thanks a lot.

If you don't mind me asking - what color scheme and font do you use? :)

from diagnose.

Also, I didn't mean 3 consecutive dots exactly, the more spaced out dots you already used to have are perfectly fine!

from diagnose.

This indeed looks better with single dots. I didn't quite like the ellipsis (it did not align well, and the ASCII equivalent looked horrible):

If you don't mind me asking - what color scheme and font do you use? :)

I am using the colorscheme Nord (the dark variant) and the font Iosevka Nerd. 🙂
I really like Nord and based my whole desktop theme on it!

from diagnose.