From: James N. V. Cash <james.nvc@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: , emacs-devel@gnu.org
Subject: Re: [PATCH] avoid hard-coded assumptions in image scaling
Date: Sun, 02 May 2021 16:56:33 -0400 [thread overview]
Message-ID: <87bl9sonwe.fsf@gmail.com> (raw)
In-Reply-To: <87fsz4g8pm.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> The point of the heuristic here is that we want to scale images up on
> HiDPI screens, so the current code gives me a scaling factor of 2.3.
> (I've got a 14" 4K screen.)
Oh, okay, that makes sense! I'm trying to track down why I've been
seeing unexpected svg rendering issues on a 4k screen and came across
this in the process.
Sorry for the incorrect patch then!
prev parent reply other threads:[~2021-05-02 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 20:18 [PATCH] avoid hard-coded assumptions in image scaling James N. V. Cash
2021-05-02 20:51 ` Lars Ingebrigtsen
2021-05-02 20:56 ` James N. V. Cash [this message]
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=87bl9sonwe.fsf@gmail.com \
--to=james.nvc@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/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).