From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: larsi@gnus.org, triska@metalevel.at, 52931@debbugs.gnu.org
Subject: bug#52931: 27.1; image-size sometimes yields a wrong image size in pixels
Date: Thu, 29 Sep 2022 16:28:57 +0300 [thread overview]
Message-ID: <83mtaifgx2.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkU0V0GKMawJgrr=zBCXnEVwU0x46ZZgpb-d2668SumTQ@mail.gmail.com> (message from Stefan Kangas on Thu, 29 Sep 2022 06:15:01 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 29 Sep 2022 06:15:01 -0700
> Cc: larsi@gnus.org, 52931@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > No, it doesn't do that. It looks up relative file names along
> > image-load-path. The reason is that image files are many times
> > displayed on the tool bar and the fringes, which are not specific to a
> > buffer, and thus we cannot possibly ensure default-directory is always
> > set to the right place when we display those.
>
> The `create-image' docstring says:
>
> Image file names that are not absolute are searched for in the
> "images" sub-directory of ‘data-directory’ and
> ‘x-bitmap-file-path’ (in that order).
>
> Does this need clarifying?
I added a more accurate sentence there:
"Create an image from FILE-OR-DATA.
FILE-OR-DATA is an image file name or image data. If it is a relative
file name, the function will look for it along `image-load-path'.
But I failed to remove the one you mention, which is somewhat
misleading. Now done.
next prev parent reply other threads:[~2022-09-29 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 17:00 bug#52931: 27.1; image-size sometimes yields a wrong image size in pixels Markus Triska
2022-01-01 17:09 ` Eli Zaretskii
2022-09-27 17:28 ` Lars Ingebrigtsen
2022-09-28 17:24 ` Markus Triska
2022-09-28 17:28 ` Lars Ingebrigtsen
2022-09-28 18:09 ` Markus Triska
2022-09-28 18:43 ` Eli Zaretskii
2022-09-28 18:57 ` Markus Triska
2022-09-28 19:12 ` Eli Zaretskii
2022-09-28 20:09 ` Markus Triska
2022-09-29 5:44 ` Eli Zaretskii
2022-09-29 13:15 ` Stefan Kangas
2022-09-29 13:28 ` Eli Zaretskii [this message]
2022-09-28 19:10 ` 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=83mtaifgx2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52931@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefankangas@gmail.com \
--cc=triska@metalevel.at \
/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).