From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 40909@debbugs.gnu.org
Subject: bug#40909: eww: Add max width option similar to Man-width-max
Date: Tue, 05 May 2020 09:37:53 +0200 [thread overview]
Message-ID: <875zdax25q.fsf@gnus.org> (raw)
In-Reply-To: <877dxu3wk4.fsf@stefankangas.se> (Stefan Kangas's message of "Sat, 02 May 2020 22:34:51 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> Not in my use, at least, it doesn't mean that. I configure everything
> to be 80 columns wide, if at all possible. Long lines are very
> annoying, arguably probably even more so in my use-case than in
> others.
Yeah, that's the usage pattern I'd expect -- you have a window that is
the width you're most comfortable with, and then shr renders using that
width, surely?
If shr uses a width wider than the window in this scenario, that's a bug
in shr.
The problem with defaulting shr-width to anything in particular is that
the rendering will be wonky if you then have a window that's narrower
than that.
I think introducing a new variable, shr-max-width, might perhaps be
nice? That is, no matter how wide a window you have, nobody probably
wants to read HTML formatted wider than that.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-05-05 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 18:24 bug#40909: eww: Add max width option similar to Man-width-max Stefan Kangas
2020-04-27 19:01 ` Eli Zaretskii
2020-04-27 19:20 ` Stefan Kangas
2020-04-27 19:39 ` Eli Zaretskii
2020-04-30 4:18 ` Lars Ingebrigtsen
2020-04-30 7:18 ` Stefan Kangas
2020-04-30 4:15 ` Lars Ingebrigtsen
2020-04-30 7:09 ` Stefan Kangas
2020-04-30 22:00 ` Lars Ingebrigtsen
2020-05-02 20:34 ` Stefan Kangas
2020-05-05 7:37 ` Lars Ingebrigtsen [this message]
2020-05-05 10:08 ` Stefan Kangas
2020-07-17 13:45 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zdax25q.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=40909@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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/emacs.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).