unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Glenn Morris <rgm@gnu.org>
Cc: 14358@debbugs.gnu.org
Subject: bug#14358: Option to use GraphicsMagick instead of ImageMagick
Date: Sat, 30 Oct 2021 09:37:23 -0700	[thread overview]
Message-ID: <CADwFkmnfG-yMVcCtqXQnE38gNZwxqPi3MMD+JtAt=NEyWR5how@mail.gmail.com> (raw)
In-Reply-To: <0n609nqjnw.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 03 Dec 2017 22:03:15 -0500")

Glenn Morris <rgm@gnu.org> writes:

> Is it possible/desirable for Emacs to be able to use GraphicsMagick
> instead of ImageMagick? I'm assuming they provide the same
> functionality, but I know nothing about it.
>
> I has a rough'n'ready go at the trivial stuff (see below), but then gave
> up with these errors:

Glenn Morris <rgm@gnu.org> writes:

> There's no interest in addressing this issue. Closing as wontfix.

Given that we are now no longer recommending ImageMagick, perhaps
GraphicsMagick support feels more relevant now than it used to?

From my point of view, GraphicsMagick has better performance, half as
many dependencies, and way fewer CVE's.  Like ImageMagick, it also gives
us "free" support for a ton of different image formats, and "free" new
ones in the future.

On the flip-side, I personally get by just fine with our built-in
support for JPEG, GIF, SVG, PNG and some others (this list will include
WEBP in Emacs 29.1).  So I have no idea what need our users have for
support for a wider range of image formats.

One final consideration is that GraphicsMagick support could be a step
towards making our ImageMagick support obsolete.





  reply	other threads:[~2021-10-30 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  7:12 bug#14358: Option to use GraphicsMagick instead of ImageMagick Glenn Morris
2017-12-04  3:03 ` Glenn Morris
2021-10-30 16:37   ` Stefan Kangas [this message]
2021-11-03  3:16     ` Richard Stallman
2021-11-03  3:54       ` Stefan Kangas
2021-11-05  3:52         ` Richard Stallman

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='CADwFkmnfG-yMVcCtqXQnE38gNZwxqPi3MMD+JtAt=NEyWR5how@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=14358@debbugs.gnu.org \
    --cc=rgm@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).