unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Fri, 01 May 2020 00:00:57 +0200	[thread overview]
Message-ID: <87wo5wzl9i.fsf@gnus.org> (raw)
In-Reply-To: <87ees578mo.fsf@stefankangas.se> (Stefan Kangas's message of "Thu, 30 Apr 2020 09:09:03 +0200")

Stefan Kangas <stefan@marxist.se> writes:

>> I'm sorry, I don't quite understand what you mean.  Why would reading
>> anything be more difficult on HiDPI monitors?
>
> Sorry, I mean on a large monitor with e.g. 16:9 aspect ratio.

Oh, with the frames full-width?  It didn't even occur to me that anybody
would do something like that.  :-)

Is that a thing people do?  I mean...  why?  That'll leave a lot of
unused screen real estate for most things Emacs displays.

But, yes, rendering web pages very wide is usually not good for
readability, but...  if a person has decided to have full-width frames,
doesn't that also mean that that person likes to have really long lines?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-04-30 22:00 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 [this message]
2020-05-02 20:34       ` Stefan Kangas
2020-05-05  7:37         ` Lars Ingebrigtsen
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=87wo5wzl9i.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).