From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Christoph Newsgroups: gmane.emacs.devel Subject: Re: imagemagick support on W32 Date: Fri, 01 Oct 2010 06:12:35 -0600 Message-ID: <4CA5D033.5010503@gmail.com> References: <4CA53CE5.1020702@gmail.com> <4CA54727.6010900@gmail.com> <4CA54834.4020106@gmail.com> <4CA54E67.5040703@gmail.com> <4CA560A0.50901@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1285935238 13949 80.91.229.12 (1 Oct 2010 12:13:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 1 Oct 2010 12:13:58 +0000 (UTC) Cc: Juanma Barranquero , emacs-devel@gnu.org To: joakim@verona.se Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 01 14:13:57 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P1eUu-0003xI-M5 for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 14:13:56 +0200 Original-Received: from localhost ([127.0.0.1]:35511 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1eUu-0001qC-4I for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 08:13:56 -0400 Original-Received: from [140.186.70.92] (port=48234 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1eUG-0001mF-Mr for emacs-devel@gnu.org; Fri, 01 Oct 2010 08:13:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P1eTg-0006o9-Ew for emacs-devel@gnu.org; Fri, 01 Oct 2010 08:13:16 -0400 Original-Received: from mail-iw0-f169.google.com ([209.85.214.169]:53122) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P1eTg-0006o2-BH for emacs-devel@gnu.org; Fri, 01 Oct 2010 08:12:40 -0400 Original-Received: by iwn33 with SMTP id 33so5831844iwn.0 for ; Fri, 01 Oct 2010 05:12:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=jH77ILeMYuVI0hwXT72fVkVdu/0eDOsuhjqQSqDEkoo=; b=I6xyNBqocjK5yS6q4zlM0Rnzm+Ez5rBS7WswQPj2MIUjj6eZ5p7dJvrZK/c+DUcNjW Jnl/1G8lw2fsWb2yepTdIU1uJmRUZv2ysjPGwsxPQtWBBs+fCzmhHnXhymM5AkAFwnnD 4GCTB0FQeoOQqjr6oHYV6oeq/fDCBVODVpznc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=RPpYXzkJobahlpORZ4F3XPLSCH07WZyjvCARoUzDIwB9NfgdZrK/Egi7ez5m2Y9sme cVWtmFMGdW+NLonF1cLpCm4f1UTzouZH3OF5+8FcJAPrEYet8hMwuo2Z1l4yttizsDy3 oaOqdQjmSyGR4Y0/Oo+viXu04YPdxE+JqP2pw= Original-Received: by 10.231.159.203 with SMTP id k11mr5542331ibx.115.1285935158648; Fri, 01 Oct 2010 05:12:38 -0700 (PDT) Original-Received: from [192.168.1.5] (67-41-203-171.hlrn.qwest.net [67.41.203.171]) by mx.google.com with ESMTPS id u3sm1145085ibu.0.2010.10.01.05.12.37 (version=SSLv3 cipher=RC4-MD5); Fri, 01 Oct 2010 05:12:37 -0700 (PDT) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:131153 Archived-At: On 10/1/2010 5:36 AM, 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. > ImageMagick support does not deactivate the other loaders. They all live > together. Of course there will then be situations when its not clear > which loader should be used, because there are several candidates > available. The ImageMagick loader can be configured so it does not try > to load particular image formats, with imagemagick-types-inhibit. Which > particular loader gets used in a particular case is not completely > obvious however. I've made no attempt to change loader priorities, and > Imagemagick usualy gets last shot at loading a format, so when jpeg > support is compiled in, and imagemagick support is compiled in, the jpeg > loader wins by default. What if jpeg support is compiled in, but the library is unavailable (dll missing). Does it also go on to ImageMagick (if their dll is availble instead)?