unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 51596@debbugs.gnu.org
Subject: bug#51596: image-transform-resize has inconsistent semantics wrt scaling up/down
Date: Thu, 04 Nov 2021 23:52:40 +0100	[thread overview]
Message-ID: <87ee7vpm87.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmkQOcpT98jUmadRhpOCgwmkae5MVP=exeBhj_MjhnurUg@mail.gmail.com> (Stefan Kangas's message of "Thu, 4 Nov 2021 11:52:16 -0700")

Stefan Kangas <stefan@marxist.se> writes:

> Right, and that's a valid use case of course.  I still find the
> interface inconsistent, as the naming scheme suggests that these three
> options should behave similarly.

Yes.  I think that, basically, the fit to height/width commands are
pretty useless -- nobody wants that, because it'll inevitably make some
images impossible to view.

The two cases that make sense are "scale down so I can see the images"
and "both scale down and scale up, because I want to see as much detail
as possible".

> Perhaps we could even have a "smart" option that only scales images up
> larger than some height and width, and otherwise leaves them in their
> original size.  That's probably the one I would like to use, now that I
> think about it.  (I usually prefer to scale images up, but as you point
> out it's pretty useless to scale small icons to fit the window.)

Sure, or a "don't scale up more than 200%", perhaps.  That's less
finicky, I think.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2021-11-04 22:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  4:14 bug#51596: image-transform-resize has inconsistent semantics wrt scaling up/down Stefan Kangas
2021-11-04 17:50 ` 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 [this message]
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=87ee7vpm87.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=51596@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).