unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: 51596@debbugs.gnu.org
Subject: bug#51596: image-transform-resize has inconsistent semantics wrt scaling up/down
Date: Wed, 3 Nov 2021 21:14:58 -0700	[thread overview]
Message-ID: <CADwFkm=E_H-FAxs=8wqLuLceykWzZxFW8X=bN5Ux-wQtcwFYTQ@mail.gmail.com> (raw)

I find the semantics of `image-transform-resize' inconsistent.  That
also goes for `image-auto-resize' and the corresponding functions.

"Fit height" and "fit width" both scales an image up or down, but "fit
height and width" only scales an image down.  Is that intentional?

I would have expected that they all scale in the same way, i.e. they
should all either scale up or down, or scale down only, or scale up
only.

My preference is that they scale both up or down, no matter which kind
of fitting you ask for.  The below diff seems to achieve what I want.
However, I'm not sure if the semantics should be changed in this way,
as I don't know if the old semantics were intentional or not.


diff --git a/lisp/image-mode.el b/lisp/image-mode.el
index 4a326cdc69..97efd8254d 100644
--- a/lisp/image-mode.el
+++ b/lisp/image-mode.el
@@ -880,7 +880,7 @@ image-toggle-display-image
                                   :format (and filename data-p))
 		  (create-image file-or-data type data-p :scale 1
 				:max-width max-width
-				:max-height max-height
+                                :height max-height
                                 ;; Type hint.
                                 :format (and filename data-p))))





             reply	other threads:[~2021-11-04  4:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  4:14 Stefan Kangas [this message]
2021-11-04 17:50 ` bug#51596: image-transform-resize has inconsistent semantics wrt scaling up/down Lars Ingebrigtsen
2021-11-04 18:52   ` Stefan Kangas
2021-11-04 19:16     ` Juri Linkov
2021-11-04 19:41       ` Stefan Kangas
2021-11-04 19:49         ` Juri Linkov
2021-11-04 20:19           ` Stefan Kangas
2021-11-04 22:52     ` Lars Ingebrigtsen
2021-11-05  4:07       ` Stefan Kangas
2021-11-05 13:22         ` Lars Ingebrigtsen
2021-11-06 18:49           ` Juri Linkov
2021-11-06 19:49             ` Stefan Kangas

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='CADwFkm=E_H-FAxs=8wqLuLceykWzZxFW8X=bN5Ux-wQtcwFYTQ@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=51596@debbugs.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).