From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37630@debbugs.gnu.org
Subject: bug#37630: 27.0.50; image-mode-fit-frame doesn't
Date: Wed, 09 Oct 2019 21:09:30 +0200 [thread overview]
Message-ID: <87v9sx68id.fsf@gnus.org> (raw)
In-Reply-To: <83y2xvw5i1.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 08 Oct 2019 19:45:26 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> We don't want to have half a line at the bottom of the frame.
>
> But that's only possible when resizing pixel-wise, no?
Yes, we could compute based on pixels, and then resize based on how many
lines that would be. But I wonder whether the mapping from pixels to
lines would run into the same problems as just counting lines does.
>> I don't really understand the utility of this command, though.
>
> I think it was written to allow popping up frames with minimal/no
> decorations that show only the image. But that's a guess.
Perhaps it was meant as a way to quickly expand the frame to display all
of the image? In the olden days, you couldn't shrink images, so perhaps
making the frame bigger momentarily was seen as a feature.
But just guessing.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-09 19:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 9:10 bug#37630: 27.0.50; image-mode-fit-frame doesn't Eli Zaretskii
2019-10-07 3:59 ` Lars Ingebrigtsen
2019-10-07 5:10 ` Eli Zaretskii
2019-10-07 5:15 ` Lars Ingebrigtsen
2019-10-07 5:31 ` Lars Ingebrigtsen
2019-10-07 16:25 ` Eli Zaretskii
2019-10-08 8:43 ` martin rudalics
2019-10-08 9:13 ` Eli Zaretskii
2019-10-08 9:25 ` martin rudalics
2019-10-08 11:53 ` Eli Zaretskii
2019-10-09 18:12 ` martin rudalics
2019-10-08 15:47 ` Lars Ingebrigtsen
2019-10-08 16:02 ` Eli Zaretskii
2019-10-08 16:12 ` Lars Ingebrigtsen
2019-10-08 16:45 ` Eli Zaretskii
2019-10-09 19:09 ` Lars Ingebrigtsen [this message]
2022-03-23 13:18 ` Lars Ingebrigtsen
2022-03-23 14:29 ` Eli Zaretskii
2022-03-23 14:34 ` Lars Ingebrigtsen
2022-03-23 14:35 ` Lars Ingebrigtsen
2022-03-23 14:50 ` Eli Zaretskii
2022-03-23 14:55 ` Lars Ingebrigtsen
2022-03-23 15:04 ` Eli Zaretskii
2022-03-23 17:07 ` martin rudalics
2022-03-23 17:30 ` Lars Ingebrigtsen
2022-03-24 8:16 ` martin rudalics
2022-03-24 9:00 ` 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=87v9sx68id.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37630@debbugs.gnu.org \
--cc=eliz@gnu.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).