From: Mark H Weaver <mhw@netris.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,
zimoun <zimon.toutoune@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: Thu, 20 May 2021 12:26:59 -0400 [thread overview]
Message-ID: <87mtspxte9.fsf@netris.org> (raw)
In-Reply-To: <87mtspzfxp.fsf@gmail.com>
Hi Maxim,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Mark H Weaver <mhw@netris.org> writes:
>
>> 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
>
> Friendly ping; it seems not much is missing to close this issue? :-).
<https://issues.guix.gnu.org/43159> is still essentially unreadable in
Emacs Eww and Lynx, as well as Dillo when CSS is disabled, because there
are many missing line breaks.
Thanks,
Mark
--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>.
next prev parent reply other threads:[~2021-05-20 16:29 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 [this message]
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=87mtspxte9.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 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.