From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: imagemagic in image-mode and image-dired-thumbnail-mode? Date: Mon, 15 Jul 2013 13:15:21 +0900 Message-ID: <8761wctq5i.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87a9lp8uxk.fsf@gmail.com> <87ehb1bbvf.fsf@gmail.com> <83ehb052k1.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1373861752 28107 80.91.229.3 (15 Jul 2013 04:15:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 15 Jul 2013 04:15:52 +0000 (UTC) Cc: Lars Magne Ingebrigtsen , spinuvit@gmail.com, joakim@verona.se, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 15 06:15:52 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UyaCP-0003dK-EI for ged-emacs-devel@m.gmane.org; Mon, 15 Jul 2013 06:15:45 +0200 Original-Received: from localhost ([::1]:47684 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UyaCO-0002aS-8m for ged-emacs-devel@m.gmane.org; Mon, 15 Jul 2013 00:15:44 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UyaCG-0002Xw-Su for emacs-devel@gnu.org; Mon, 15 Jul 2013 00:15:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UyaCG-0006Fj-0i for emacs-devel@gnu.org; Mon, 15 Jul 2013 00:15:36 -0400 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:40948) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UyaCE-000636-GY; Mon, 15 Jul 2013 00:15:34 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id A740297099A; Mon, 15 Jul 2013 13:15:21 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 6A61615805A; Mon, 15 Jul 2013 13:15:21 +0900 (JST) In-Reply-To: <83ehb052k1.fsf@gnu.org> X-Mailer: VM undefined under 21.5 (beta32) "habanero" b0d40183ac79 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:161892 Archived-At: Eli Zaretskii writes: > How about taking out the ImageMagick code that does the scaling and > rolling it into Emacs? How hard can that be? > > Or maybe there's some other library out there that we could use to > roll our own image scaling code. I don't believe for a moment that > ImageMagick is the only one that is able to pull that. Eli, are you proposing to do the work yourself? If not, ImageMagick (or GraphicsMagick, which has the goal of being more stable, dunno if it succeeds) are plausible strategies for getting more features for less Emacs code, and probably less work. (There were some other candidates such as imlib, but I haven't followed graphics libraries for over ten years.) XEmacs did try the same strategy with ImageMagick and abandoned it (too unstable, too many undocumented crashers) -- but that was over ten years ago. Surely ImageMagick has improved over the years. Note also that the decision to abandon was made by the guy who implemented in the first place. If the current Lisp protection from the PDF crashes isn't good enough, add a filter at the C level so Lisp *can't* pass PDFs to ImageMagick (or tell the ImageMagick advocates it will be removed or deprecated if they don't, which IMO is a reasonable condition, although I probably wouldn't require it myself). The other issues (handling of advanced features like multi-image GIFs ) probably aren't really bugs, but rather simply unimplemented. I have to wonder how important those are....