From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: imagemagick format detection code Date: Tue, 13 Aug 2013 10:23:32 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1376403837 10356 80.91.229.3 (13 Aug 2013 14:23:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Aug 2013 14:23:57 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 13 16:23:58 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 1V9FVp-0001Ze-Mh for ged-emacs-devel@m.gmane.org; Tue, 13 Aug 2013 16:23:53 +0200 Original-Received: from localhost ([::1]:47998 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9FVp-0001qL-6j for ged-emacs-devel@m.gmane.org; Tue, 13 Aug 2013 10:23:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46757) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9FVd-0001q4-Pt for emacs-devel@gnu.org; Tue, 13 Aug 2013 10:23:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V9FVV-0000aV-CO for emacs-devel@gnu.org; Tue, 13 Aug 2013 10:23:41 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60801) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9FVV-0000aR-9B for emacs-devel@gnu.org; Tue, 13 Aug 2013 10:23:33 -0400 Original-Received: from [98.143.210.201] (port=52721 helo=ceviche.home) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1V9FVR-0000uq-Vs; Tue, 13 Aug 2013 10:23:31 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 9B8EF663DD; Tue, 13 Aug 2013 10:23:32 -0400 (EDT) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Mon, 12 Aug 2013 17:17:39 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:162655 Archived-At: > Or we could explicit and call it :content-type, since that's what it > is. But that may lead callers to expect that it (always) be heeded > instead of treating it as a hint. Uhm... :content-type-hint? I like content-type in the sense that I'd like to see it used as an intermediate step between file names and major modes. But I'm not sure it's the right thing here. > '(("image/x-icon" "ico")) For example, here we end up using a non-official content-type because there's no official content-type for it. This said, it's probably no worse than hacking up our own classification, so... yes, I guess it's a good plan. But please make them be symbols rather than strings: '((image/x-icon . "ico")) >> We currently have a bit of a mess wrt to use of "format" and "type" >> since they're both used currently to refer to the same thing, which is >> not really the type or format of the image but rather something like the >> rendering library used. > Yes. This will add to the general confusion in this area. We should at least rework the doc to use "type" everywhere, so we can use :format for the new notion. Stefan