all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Vitaliy Shatrov <guix.vits@disroot.org>
Cc: 43166@debbugs.gnu.org
Subject: bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.
Date: Thu, 3 Sep 2020 18:11:35 +0200	[thread overview]
Message-ID: <CAJ3okZ1yGdsZx6pqMkYPQGFHWcQ=uCtBJA0aNE+kNVRAYC=UHQ@mail.gmail.com> (raw)
In-Reply-To: <73F56D6B-6448-44C2-8EB9-23AE854AD4CF@disroot.org>

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




  parent reply	other threads:[~2020-09-03 16:20 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 [this message]
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
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='CAJ3okZ1yGdsZx6pqMkYPQGFHWcQ=uCtBJA0aNE+kNVRAYC=UHQ@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=43166@debbugs.gnu.org \
    --cc=guix.vits@disroot.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 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.