all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>, 43166@debbugs.gnu.org
Subject: bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.
Date: Fri, 10 Dec 2021 17:05:00 -0500	[thread overview]
Message-ID: <87o85o2k0o.fsf@netris.org> (raw)
In-Reply-To: <87sfv1skir.fsf@elephly.net>

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> 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 still be reflown.
>
> Sorry for the delay, but there was no way for me to take enough time to
> work on mumi before.  You are all still more than welcome to contribute
> to mumi.

No worries.  Thanks very much for fixing it!

> 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 <https://issues.guix.gnu.org/43159> with EWW, and the
line breaks in the diffs are still missing, making the diffs unreadable.
I also fetched the same URL with Wget, and there are no <pre> elements
within.  Any idea what's going on?

Anyway, thanks again for fixing this issue in Mumi.

     Regards,
       Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.




  reply	other threads:[~2021-12-10 22:06 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 [this message]
2021-12-10 22:08     ` Ricardo Wurmus
2021-12-13  0:59   ` Mark H Weaver
2021-12-13  7:57     ` Ricardo Wurmus
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

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

  git send-email \
    --in-reply-to=87o85o2k0o.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=43166@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.