unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: 43166@debbugs.gnu.org
Subject: bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.
Date: Mon, 13 Dec 2021 07:57:47 +0000	[thread overview]
Message-ID: <87zgp5lylo.fsf@elephly.net> (raw)
In-Reply-To: <87k0g92uaw.fsf@netris.org>


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
> putting the entire patch within a single 'pre' element.

It does indeed wrap each line, because otherwise we can’t style the
lines e.g. to highlight additions with green and deletions with red.

People who use Emacs anyway will have Emacs apply its own fontification,
so that’s of no use to them.  But people who use Emacs would probably
want to use the Emacs interface to Debbugs anyway.

The extra spacing between lines as seen in EWW is not intentional, and I
did not see this in my local tests.  (Perhaps different patches render
differently in EWW?)  I’ll add this to my TODO list.

> As a result, for users of EWW or Lynx, Mumi is still far inferior to the
> web interface of Debian's bug tracking system (used by bugs.gnu.org).

Note that you can also view the raw messages.  Every message part has
its own link; following that link you can see the unstyled plain text
rendering.

There’s nothing wrong with the sample HTML you posted.  Yes, mumi’s is
more verbose than just wrapping text in <pre>…</pre> because we need
more markup to tell browsers how to style the patch.

-- 
Ricardo




  reply	other threads:[~2021-12-13  8:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  5:16 bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m Vitaliy Shatrov
2020-09-02 17:24 ` Mark H Weaver
2020-09-02 18:18   ` Mark H Weaver
2020-09-03 16:11 ` zimoun
2020-09-05 14:17   ` Vitaliy Shatrov
2020-09-14 13:03     ` Maxim Cournoyer
2020-09-14 20:55       ` Mark H Weaver
2020-09-14 21:17         ` zimoun
2020-09-14 21:53           ` Ricardo Wurmus
2020-09-15  1:06             ` Ricardo Wurmus
2020-09-15  9:51               ` Jan Nieuwenhuizen
2020-09-15 10:13             ` Mark H Weaver
2020-09-15 10:28               ` Mark H Weaver
2021-05-20 13:35                 ` Maxim Cournoyer
2021-05-20 16:26                   ` Mark H Weaver
2021-05-20 19:23                     ` Maxim Cournoyer
2021-12-09 18:20 ` Ricardo Wurmus
2021-12-10 22:05   ` Mark H Weaver
2021-12-10 22:08     ` Ricardo Wurmus
2021-12-13  0:59   ` Mark H Weaver
2021-12-13  7:57     ` Ricardo Wurmus [this message]
2021-12-16  6:19       ` Mark H Weaver
2021-12-13  5:50   ` Jan Nieuwenhuizen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgp5lylo.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=43166@debbugs.gnu.org \
    --cc=mhw@netris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).