unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Image formats support
Date: Sun, 19 Mar 2017 00:08:13 +0100	[thread overview]
Message-ID: <CAFgFV9PMz0=X8ezf0aO1FVfUELh98vTMBiqZqcomtLsN9BPwDQ@mail.gmail.com> (raw)
In-Reply-To: <87var6z1sc.fsf@luca>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

2017-03-18 22:57 GMT+01:00 Andreas Politz <politza@hochschule-trier.de>:

>
> Is there a down-side to this, apart from the exe becoming a little bigger
> ?


I run Windows so the exe is not bigger because the dlls are dynamically
loaded.
My problem is rather  about emacs configuration. Various packages are able
to generate
preview images on the fly. How a normal user will know that ImageMagick or
libpng
will render those images ? How to switch from one to the other if needed ?
Or should ImageMagick supersede everything else when it is available ?

Also some packages call mogrify to resize images. If emacs is compiled with
ImageMagick support, surely the cost of calling an external program can be
spared.

I had the feeling that when ImageMagick support is compiled in, the other
graphic format
libraries could be removed. But that may not be that simple.
I hoped that someone had a good overview of the various options and comment
on that
feeling.

Fabrice

[-- Attachment #2: Type: text/html, Size: 1450 bytes --]

      reply	other threads:[~2017-03-18 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 13:38 Image formats support Fabrice Popineau
2017-03-18 14:27 ` Andreas Politz
2017-03-18 15:00   ` Fabrice Popineau
2017-03-18 15:44     ` Andreas Politz
2017-03-18 15:49       ` Fabrice Popineau
2017-03-18 16:24         ` Andreas Politz
2017-03-18 14:34 ` joakim
2017-03-18 14:49 ` Clément Pit-Claudel
2017-03-18 21:57 ` Andreas Politz
2017-03-18 23:08   ` Fabrice Popineau [this message]

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='CAFgFV9PMz0=X8ezf0aO1FVfUELh98vTMBiqZqcomtLsN9BPwDQ@mail.gmail.com' \
    --to=fabrice.popineau@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=politza@hochschule-trier.de \
    /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).