From: joakim@verona.se
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Christoph <cschol2112@googlemail.com>, emacs-devel@gnu.org
Subject: Re: imagemagick support on W32
Date: Fri, 01 Oct 2010 22:44:37 +0200 [thread overview]
Message-ID: <m3zkuxd4ne.fsf@verona.se> (raw)
In-Reply-To: <AANLkTikgUBYCrzJN-i704Qxox2Eo1paoTb0QB5Utk35n@mail.gmail.com> (Juanma Barranquero's message of "Fri, 1 Oct 2010 21:51:17 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> On Fri, Oct 1, 2010 at 13:36, <joakim@verona.se> wrote:
>
>> I'm not sure what the original question was, but I intended for
>> ImageMagick support to live alongside the other image loaders.
>
> OK.
>
>> There is, (imagemagick-types). You dont know for certain at compile time
>> which formats are available, because imagemagick supports a plugin
>> mechanism for new formats.
>
> How does that integrate with image-types and image-type-available-p?
Uhm, aparently not at all? Something must have gotten lost somewhere...
>> so when jpeg
>> support is compiled in, and imagemagick support is compiled in, the jpeg
>> loader wins by default.
>
> Seems sensible.
>
> Thanks for explaining this,
>
> Juanma
--
Joakim Verona
next prev parent reply other threads:[~2010-10-01 20:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 1:44 imagemagick support on W32 Christoph
2010-10-01 1:52 ` Juanma Barranquero
2010-10-01 2:27 ` Christoph
2010-10-01 2:32 ` Christoph
2010-10-01 2:58 ` Christoph
2010-10-01 3:16 ` Juanma Barranquero
2010-10-01 4:16 ` Christoph
2010-10-01 7:30 ` Eli Zaretskii
2010-10-01 10:37 ` Juanma Barranquero
2010-10-01 11:36 ` joakim
2010-10-01 12:12 ` Christoph
2010-10-01 12:38 ` joakim
2010-10-01 19:57 ` Juanma Barranquero
2010-10-01 20:41 ` joakim
2010-10-02 3:31 ` Jason Rumney
2010-10-01 19:51 ` Juanma Barranquero
2010-10-01 20:44 ` joakim [this message]
2010-10-01 20:53 ` Juanma Barranquero
2010-10-01 12:04 ` Christoph
2010-10-01 19:55 ` Juanma Barranquero
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=m3zkuxd4ne.fsf@verona.se \
--to=joakim@verona.se \
--cc=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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.