From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Thomas Hühn" <t@2uo.de>, 58101@debbugs.gnu.org
Subject: bug#58101: 28.2; image-size nonsensical
Date: Tue, 27 Sep 2022 13:57:16 +0200 [thread overview]
Message-ID: <87edvx3u8z.fsf@gnus.org> (raw)
In-Reply-To: <83a66ljgwb.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 27 Sep 2022 12:39:00 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> >> After some googling I found image-scaling-factor, and after setting that
>> >> to 1, I always get the expected 1291 . 632 now.
>> >
>> > So the issue happens because image-scaling-factor is different from 1?
>> > If so, this doesn't seem to be a bug, does it?
>>
>> I cannot reproduce the bug today, but the result until yesterday (as
>> written in the bug report) was wrong, even taking image-scaling-factor
>> into account (30 . 30).
>
> Well, we need a reproducible recipe to investigate, I think.
Can you try
(image-size (create-image "/tmp/two_key_system_2x.png" nil nil :scale 1.4) :pixels)
It rather sounds like `image-size' on Windows doesn't work when there's
scaling involved and then reports the size in character units instead.
next prev parent reply other threads:[~2022-09-27 11:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:41 bug#58101: 28.2; image-size nonsensical Thomas Hühn
2022-09-27 6:05 ` Eli Zaretskii
2022-09-27 9:00 ` Thomas Hühn
2022-09-27 9:19 ` Eli Zaretskii
2022-09-27 9:21 ` Thomas Hühn
2022-09-27 9:39 ` Eli Zaretskii
2022-09-27 11:57 ` Lars Ingebrigtsen [this message]
2022-09-27 12:14 ` Eli Zaretskii
2022-09-27 12:25 ` Thomas Hühn
2022-09-27 12:28 ` Lars Ingebrigtsen
2022-09-27 12:30 ` Thomas Hühn
2022-09-27 12:36 ` Lars Ingebrigtsen
2022-09-27 12:50 ` Thomas Hühn
2022-09-27 12:51 ` Lars Ingebrigtsen
2022-09-27 14:28 ` Stefan Kangas
2022-09-27 15:41 ` Lars Ingebrigtsen
2022-09-27 15:42 ` Eli Zaretskii
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=87edvx3u8z.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58101@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=t@2uo.de \
/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).