unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37630@debbugs.gnu.org
Subject: bug#37630: 27.0.50; image-mode-fit-frame doesn't
Date: Wed, 23 Mar 2022 16:29:25 +0200	[thread overview]
Message-ID: <83a6dgeo8q.fsf@gnu.org> (raw)
In-Reply-To: <871qysajss.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  23 Mar 2022 14:18:59 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: rudalics@gmx.at,  37630@debbugs.gnu.org
> Date: Wed, 23 Mar 2022 14:18:59 +0100
> 
> Lars Ingebrigtsen <larsi@gnus.org> writes:
> 
> > 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've now rewritten the command to use pixels, and that seems to fix the
> issue on a couple of configurations here, at least.

Thanks, it's much better now.  Although the second
image-mode-fit-frame doesn't restore the original dimensions: I get a
frame that is 2 lines too high wrt the original one.





  reply	other threads:[~2022-03-23 14:29 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
2022-03-23 13:18                     ` Lars Ingebrigtsen
2022-03-23 14:29                       ` Eli Zaretskii [this message]
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=83a6dgeo8q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37630@debbugs.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).