unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Thomas Hühn" <t@2uo.de>, "Eli Zaretskii" <eliz@gnu.org>,
	58101@debbugs.gnu.org
Subject: bug#58101: 28.2; image-size nonsensical
Date: Tue, 27 Sep 2022 17:41:25 +0200	[thread overview]
Message-ID: <877d1o3jve.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkm=WPVFq_45XdstFKnS5FhqSK2xJK5P0HbyHAn76AEfr3Q@mail.gmail.com> (Stefan Kangas's message of "Tue, 27 Sep 2022 10:28:44 -0400")

Stefan Kangas <stefankangas@gmail.com> writes:

> Hmm, that evaluates to "(30 . 30)" here, even though I don't even have a
> file named "/tmp/two_key_system_2x.png".
>
> Isn't that a bug?  I'd expect it to signal an error.

It doesn't check whether the image exists until doing redisplay
normally (and then logs the problem in *Messages*)...  But `image-size'
could certainly signal an error in these cases, I guess.





  reply	other threads:[~2022-09-27 15:41 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
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 [this message]
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=877d1o3jve.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=58101@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefankangas@gmail.com \
    --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).