bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi Ricardo, Ricardo Wurmus writes: >> However, in both EWW and Lynx, the embedded patches are rendered >> double-spaced, i.e. there are empty lines inserted between every two >> adjacent lines of every patch. I guess that's because Mumi wraps each >> individual line within its own 'pre' and 'di

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi Mark, > However, in both EWW and Lynx, the embedded patches are rendered > double-spaced, i.e. there are empty lines inserted between every two > adjacent lines of every patch. I guess that's because Mumi wraps each > individual line within its own 'pre' and 'div' elements, instead of > putt

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Ricardo Wurmus writes: > This is now fixed in mumi. I tested the change in eww and in icecat. Lovely, thank you! Greetings, Janneke -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi Ricardo, Ricardo Wurmus writes: > This is now fixed in mumi. I tested the change in eww and in icecat. > > This was easier to implement than when the bug was first reported. Due > to later developments I could limit the use of “pre” to lines in the > “diff” context, so that message text can

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi Mark, >> I’m reconfiguring the server hosting issues.guix.gnu.org now, so this >> change will go live as soon as that’s done. > > Hmm. Your mail headers indicate that you wrote the words above more > than 27 hours ago, but the problem persists on issues.guix.gnu.org. I'm > now looking at

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi Ricardo, Ricardo Wurmus writes: > This is now fixed in mumi. I tested the change in eww and in icecat. > > This was easier to implement than when the bug was first reported. Due > to later developments I could limit the use of “pre” to lines in the > “diff” context, so that message text can

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

This is now fixed in mumi. I tested the change in eww and in icecat. This was easier to implement than when the bug was first reported. Due to later developments I could limit the use of “pre” to lines in the “diff” context, so that message text can still be reflown. Sorry for the delay, but th

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi, Mark H Weaver writes: > Hi Maxim, > > Maxim Cournoyer writes: > >> Mark H Weaver writes: >> >>> Earlier, I wrote: However, I've noticed that in Dillo with CSS disabled, generating a 'pre' for each line makes the line spacing larger than would be ideal. It seems that some ver

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi Maxim, Maxim Cournoyer writes: > Mark H Weaver writes: > >> Earlier, I wrote: >>> However, I've noticed that in Dillo with CSS disabled, generating a >>> 'pre' for each line makes the line spacing larger than would be ideal. >>> It seems that some vertical padding or margins are added around

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hello, Mark H Weaver writes: > Earlier, I wrote: >> However, I've noticed that in Dillo with CSS disabled, generating a >> 'pre' for each line makes the line spacing larger than would be ideal. >> It seems that some vertical padding or margins are added around each >> 'pre'. It's likely that ma

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Earlier, I wrote: > However, I've noticed that in Dillo with CSS disabled, generating a > 'pre' for each line makes the line spacing larger than would be ideal. > It seems that some vertical padding or margins are added around each > 'pre'. It's likely that many browsers do this in their default s

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Ricardo Wurmus writes: >> On Mon, 14 Sep 2020 at 22:58, Mark H Weaver wrote: >> >>> For what it's worth: not everyone uses Emacs, and it would be good to >>> support users who choose to use simpler software. I guess that it would >>> be quite easy to modify the software behind 'issues.guix.gnu.

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Ricardo Wurmus writes: > The attached patch seems to fix the worst problems. Ohh...thank you!!! This makes issues at least readable in EWW. It's a bit annoying to change issues URLs into bugs.gnu.org urls and this also made me reluctant to share issues URLs -- altough I greatly appreciate all t

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

The attached patch seems to fix the worst problems. I’m marking up each line in a message with a “span” tag and a “line” class; then I use CSS to visually separate the lines. Simple browsers that don’t support this CSS rely on “span” to be an inline tag; likewise they rely on “div” to be a block

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

zimoun writes: > Dear Mark, > > On Mon, 14 Sep 2020 at 22:58, Mark H Weaver wrote: > >> For what it's worth: not everyone uses Emacs, and it would be good to >> support users who choose to use simpler software. I guess that it would >> be quite easy to modify the software behind 'issues.guix.

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Dear Mark, On Mon, 14 Sep 2020 at 22:58, Mark H Weaver wrote: > For what it's worth: not everyone uses Emacs, and it would be good to > support users who choose to use simpler software. I guess that it would > be quite easy to modify the software behind 'issues.guix.gnu.org' to > generate HTML

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Maxim Cournoyer writes: > Vitaliy Shatrov writes: > > Closing since a dedicated tool for use in Emacs (emacs-debbugs) exists, > which works around the shortcomings of the Emacs web browsers (Probably > CSS related, as Mark pointed out). For what it's worth: not everyone uses Emacs, and it would

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hi Vitaliy, Vitaliy Shatrov writes: Closing since a dedicated tool for use in Emacs (emacs-debbugs) exists, which works around the shortcomings of the Emacs web browsers (Probably CSS related, as Mark pointed out). Thanks, Maxim

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Really i was a fool. Thanks for suggesting a tool. No more dances with web-faces.

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Dear, If you use Emacs, you should try the package emacs-debbugs. Then: C-u M-x debbugs-gnu guix,guix-patches n y and last M-x debbugs-gnu-bugs 43159 It does not solve the CSS and/or Javascript issue but it clearly eases the readings of bug reports with Emacs. All the best, simon

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Earlier, I wrote: > I see similar problems with both 'lynx' and 'dillo' when remote CSS is > disabled. To be clear, Lynx doesn't have CSS support, so it's unable to properly render 'issues.guix.gnu.org'. Dillo can render it unless remote CSS is disabled. Mark

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Vitaliy Shatrov writes: > Hello again dear Guixen. > I use emacs-w3m as a browser on a single board computer. I want to read, > for example, issue #43159. > > I can read it on https://debbugs.gnu.org/43159. It's formatted properly, and > the patch is readable too. > > But the https://issues.

bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.

Hello again dear Guixen. I use emacs-w3m as a browser on a single board computer. I want to read, for example, issue #43159. I can read it on https://debbugs.gnu.org/43159. It's formatted properly, and the patch is readable too. But the https://issues.guix.gnu.org/43159 is barely readable, a