From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: C file recoginzed as image file Date: Tue, 9 Jan 2007 01:19:27 +0100 Message-ID: References: <40673.128.165.123.18.1168301491.squirrel@webmail.lanl.gov> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1168301993 1801 80.91.229.12 (9 Jan 2007 00:19:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 9 Jan 2007 00:19:53 +0000 (UTC) Cc: dooglus@gmail.com, c.a.rendle@gmail.com, Stefan Monnier , rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 09 01:19:51 2007 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.50) id 1H44iO-0000PI-2A for ged-emacs-devel@m.gmane.org; Tue, 09 Jan 2007 01:19:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H44iN-0006Ge-7k for ged-emacs-devel@m.gmane.org; Mon, 08 Jan 2007 19:19:43 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H44iB-0006Fw-4z for emacs-devel@gnu.org; Mon, 08 Jan 2007 19:19:31 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H44i9-0006Dq-6D for emacs-devel@gnu.org; Mon, 08 Jan 2007 19:19:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H44i9-0006Dl-0B for emacs-devel@gnu.org; Mon, 08 Jan 2007 19:19:29 -0500 Original-Received: from [64.233.182.191] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H44i8-0004R8-Cn for emacs-devel@gnu.org; Mon, 08 Jan 2007 19:19:28 -0500 Original-Received: by nf-out-0910.google.com with SMTP id h2so2237989nfe for ; Mon, 08 Jan 2007 16:19:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=N/QfeOOad+D5LAW95Ht6jMDeXj1+wYWwWK65/OLJeUh8z9Etts/YVKsme4qyAWTvKagrf0q8SG8XnYT3zrjIS6S0McENpIPFq4/gA24jCgGFrxBARSgnbr7BQxUtKp9z1uGkW1A4Ajbj6mpFLuoB92hAXSfORcq8n8cBkz3sR3Q= Original-Received: by 10.82.120.14 with SMTP id s14mr2669882buc.1168301967577; Mon, 08 Jan 2007 16:19:27 -0800 (PST) Original-Received: by 10.82.146.7 with HTTP; Mon, 8 Jan 2007 16:19:27 -0800 (PST) Original-To: herring@lanl.gov In-Reply-To: <40673.128.165.123.18.1168301491.squirrel@webmail.lanl.gov> Content-Disposition: inline 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:65030 Archived-At: On 1/9/07, Stuart D. Herring wrote: > It's true that a JPEG image is a JPEG image, but "foo.jpg" (or even > "foo.c") is not a JPEG image, it's a file (well, a filename, but consider > the associated file). And a (seekable) file is a sequence of bytes, not > an image. An image can be constructed from it, but just as you said it's > a matter of how you treat it. I don't know about you, but I don't have "seekable sequences of bytes" in my Pictures folder. I have images (of my dogs, mostly). I use them as images: I display them, print them, send them to Flickr and pass them to other people so they can admire my dogs. That these pictures are also "seekable sequences of bytes" is an implementation detail. If I ever want to access one of these pictures from Emacs, 99,999999% of time I'll want them as images, not as any other thing. > Finally, remember that we don't have a concept of "that image" for > counting usage: this decision has to be made the first time we see a file, > regardless of its history of usage. Then the decision and heuristics should be geared towards the most common use, shouldn't it? /L/e/k/t/u