is it possible to somehow fix this, or rather where would the right fix be

No text-mode browser is likely to work reasonably well with the new diffs and text-mode browsers have never been an active target for the project. If the web-mode diffs worked in the past on such browsers, it was very likely a "happy accident." We generally only actively target HTML5-capable conventional browsers.

But diffs do work well, either side-by-side (slightly messy on a small tty, but ok) or unifined -- you even get colored cross-over lines for removed lines. This was rather when showing line numbers with a file, not diffs per see.

eww is also not a text-mode browser, it is fully capable of showing images and tables.

This was rather when showing line numbers with a file, not diffs per see.

Indeed, my apologies - i was working from a mobile device at the time and overlooked your link.

i think that can be easily improved for you without breaking the line-linking features, but i'll have to experiment with it to be certain.

If you are able to test this CSS-only patch, that would be a big help. This patch is the least intrusive option i've come up with:

Index: src/default.css
==================================================================
--- src/default.css
+++ src/default.css
@@ -1305,14 +1305,18 @@
   vertical-align: top;
   padding: 0.25em 0 0 0 /*prevents slight overlap at top */;
 }
 table.numbered-lines td.line-numbers {
   width: 4.5em;
+  white-space: pre;
 }
 table.numbered-lines td.line-numbers > span:first-of-type {
   margin-top: 0.25em/*must match top PADDING of
                       td.file-content > pre > code*/;
+}
+table.numbered-lines td.line-numbers > span::after {
+  content: "\a";
 }
 table.numbered-lines td.line-numbers > span {
   display: block;
   margin: 0;
   padding: 0;

If that doesn't work, then there's a functionally equivalent change we can make in the C code which doesn't rely on the the ::after content CSS feature.

This was rather when showing line numbers with a file, not diffs...

A presumed fix for this was just pushed to trunk. If you can, please try out that version and report any problems here. In short, the DOM structure was made to be more like that used in the diff views.

Thats lovley, it works super great! Thank you!

I'm not sure if it would be possible, and I think it works good enough. So mostly asking if those who know, might know if it is possible at all.

In text-only, the region of lines that might be pointed out in the URL isn't highlighted in any form. Is there any possibly that it could be shown in some form?

In text-only, the region of lines that might be pointed out in the URL isn't highlighted in any form. Is there any possibly that it could be shown in some form?

That's done via CSS . If it's not being highlighted or bolded, your browser isn't applying the CSS styling. We "could" use explicit <U> tags to underline those, and hope that text-mode browsers can underline the text, but that would be a step backwards for the full-fledged browsers (where we don't really want those underlined). If you can suggest a workaround which works for you and does not negatively impact full-fledged browsers then i'm willing to try it.

We "could" add an extra character to the selected lines, but that would, IMO, look horrible for non-text browsers (and the server, where that would need to be generated, does not know anything significant about the browser).

(Edit: that was weird: post got submitted twice within 1 second of each other.)

Ah, so that might be a bug in eww then of what possible highlighting it can do. Since it does work correctly for diffs, added regions are in green and removed ones are in red.

Since it does work correctly for diffs, added regions are in green and removed ones are in red.

Those are done using INS and DEL tags. Perhaps (i'm just speculating) eww can't style SPAN elements in arbitrary ways?