From: Alan Third <alan@idiocy.org>
To: Yuuki Harano <masm+emacs@masm11.me>
Cc: contovob@tcd.ie, 46491@debbugs.gnu.org
Subject: bug#46491: [feature/pgtk] Unused macro warning in image.c without ImageMagick
Date: Sun, 14 Feb 2021 10:03:25 +0000 [thread overview]
Message-ID: <YCj1bQ8GcW+iGQSJ@breton.holly.idiocy.org> (raw)
In-Reply-To: <20210214.112019.308581254652492325.masm@luna.pink.masm11.me>
On Sun, Feb 14, 2021 at 11:20:19AM +0900, Yuuki Harano wrote:
>
> On Sat, 13 Feb 2021 23:05:45 +0000,
> Alan Third <alan@idiocy.org> wrote:
> > I think your patch looks right, but I'm confused as to why this is in
> > the PGTK branch at all. The imagemagick transforms are intentionally
> > excluded from the native transforms, but this disables the imagemagick
> > transforms completely and, presumably, replaces them with native
> > transforms.
>
> I wanted to make imagemagick images not blurry in image-mode on
> scale x2.0 monitor.
>
> With the exclusion, imagemagick generates scaled image pixel data,
> and the image is rendered twice in size, so it is blurry.
> Without the exclusion, imagemagick generates original image pixel data,
> and the image may not be enlarged (but shrinked), so it may not be blurry.
>
> For other than imagemagick, like png, original image pixel data is generated,
> and it is not blurry on scale x2.0 monitor.
I am aware of this, I see the same thing on NS, but when native
transforms were introduced we decided that when a user asks
imagemagick to modify an image, imagemagick should actually do the
modifications and Emacs will just display the results.
I don't know that it's important, though.
--
Alan Third
next prev parent reply other threads:[~2021-02-14 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 16:34 bug#46491: [feature/pgtk] Unused macro warning in image.c without ImageMagick Basil L. Contovounesios
2021-02-13 23:05 ` Alan Third
2021-02-14 2:20 ` Yuuki Harano
2021-02-14 10:03 ` Alan Third [this message]
2021-02-14 15:38 ` Eli Zaretskii
2021-02-14 2:02 ` Yuuki Harano
2021-02-14 12:33 ` Basil L. Contovounesios
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YCj1bQ8GcW+iGQSJ@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=46491@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=masm+emacs@masm11.me \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.