From: Mark H Weaver <mhw@netris.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
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: Mon, 14 Sep 2020 16:55:51 -0400 [thread overview]
Message-ID: <87een4f571.fsf@netris.org> (raw)
In-Reply-To: <87ft7k5x45.fsf@gmail.com>
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Vitaliy Shatrov <guix.vits@disroot.org> 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 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 that works well with simpler web browsers, so I'd prefer
to keep this bug open. What do you think?
Mark
next prev parent reply other threads:[~2020-09-14 20:58 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 [this message]
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=87een4f571.fsf@netris.org \
--to=mhw@netris.org \
--cc=43166@debbugs.gnu.org \
--cc=guix.vits@disroot.org \
--cc=maxim.cournoyer@gmail.com \
/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.