From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>, zimoun <zimon.toutoune@gmail.com>
Cc: maxim.cournoyer@gmail.com, guix.vits@disroot.org, 43166@debbugs.gnu.org
Subject: bug#43166: The issues.guix.gnu.org is hard to read in emacs-w3m.
Date: Tue, 15 Sep 2020 06:28:31 -0400 [thread overview]
Message-ID: <87pn6nbafp.fsf@netris.org> (raw)
In-Reply-To: <87wo0vbb46.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
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 styling
> for 'pre'. With this in mind, it would perhaps be better to wrap a
> single 'pre' around each message. Then you could either (1) leave the
> lines as 'span's and add a raw CR-LF after each line (which would make
> the HTML source code more readable) or (2) change the 'span's to 'div's
> as in your proposed patch.
Actually, I just found by experimentation that option (2) above doesn't
work well in either Lynx or Dillo. Option (1) works well in the simple
browsers I've tried so far, which are Lynx, Dillo, Netsurf, and Eww.
Mark
[-- Attachment #2: Example HTML for Option 1 --]
[-- Type: text/html, Size: 175 bytes --]
[-- Attachment #3: Example HTML for Option 2 --]
[-- Type: text/html, Size: 163 bytes --]
next prev parent reply other threads:[~2020-09-15 10:30 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 [this message]
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
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=87pn6nbafp.fsf@netris.org \
--to=mhw@netris.org \
--cc=43166@debbugs.gnu.org \
--cc=guix.vits@disroot.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@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 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).