From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: [dooglus@gmail.com: display problem after renaming open image files] Date: Tue, 03 Apr 2007 10:03:33 -0400 Message-ID: <873b3hmu6i.fsf@stupidchicken.com> References: <87ircfu4eo.fsf@stupidchicken.com> <868xd998qo.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1175609066 19556 80.91.229.12 (3 Apr 2007 14:04:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 3 Apr 2007 14:04:26 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 03 16:04:04 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 1HYjc0-0002dc-Bs for ged-emacs-devel@m.gmane.org; Tue, 03 Apr 2007 16:03:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HYjf9-0004Gp-Cs for ged-emacs-devel@m.gmane.org; Tue, 03 Apr 2007 10:07:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HYjf4-0004Cz-7X for emacs-devel@gnu.org; Tue, 03 Apr 2007 10:07:02 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HYjf3-0004By-Hq for emacs-devel@gnu.org; Tue, 03 Apr 2007 10:07:01 -0400 Original-Received: from south-station-annex.mit.edu ([18.72.1.2]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HYjbt-0000OK-H8; Tue, 03 Apr 2007 10:03:45 -0400 Original-Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82]) by south-station-annex.mit.edu (8.13.6/8.9.2) with ESMTP id l33E3hU8027400; Tue, 3 Apr 2007 10:03:43 -0400 (EDT) Original-Received: from outgoing-legacy.mit.edu (OUTGOING-LEGACY.MIT.EDU [18.7.22.104]) by grand-central-station.mit.edu (8.13.6/8.9.2) with ESMTP id l33E3dcX022390; Tue, 3 Apr 2007 10:03:40 -0400 (EDT) Original-Received: from localhost (SYDNEYPACIFIC-FOUR-SEVENTY-NINE.MIT.EDU [18.95.6.224]) ) by outgoing-legacy.mit.edu (8.13.6/8.12.4) with ESMTP id l33E3XRU001893; Tue, 3 Apr 2007 10:03:39 -0400 (EDT) Original-Received: from cyd by localhost with local (Exim 3.36 #1 (Debian)) id 1HYjbh-0000wS-00; Tue, 03 Apr 2007 10:03:33 -0400 In-Reply-To: <868xd998qo.fsf@lola.quinscape.zz> (David Kastrup's message of "Tue\, 03 Apr 2007 10\:12\:47 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.96 (gnu/linux) X-Scanned-By: MIMEDefang 2.42 X-Spam-Score: -2.599 X-detected-kernel: Solaris 9.1 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:68990 Archived-At: David Kastrup writes: >> This is because the underlying image file, pic1.png, is gone. I think >> this is not worth fixing at this point. >> >> What causes this bug? What data structure still refers >> to the old file name, and has not been updated to the new one? > > The image property. And Emacs does not track the arbitrary renaming > of files outside of it. > > We can either let the image property refer to the file, or we can use > a :data property. The latter, however, would require duplicating the > image content into that property, so we'll permanently have > > a) the image buffer with the content > b) the :data property with the content > c) the image cache with the content Exactly. This would be particularly annoying considering people now routinely handle image sizes in the 10s or 100s of megabytes. If you move the underlying file outside of Emacs, there's no way for Emacs to know where you moved it; as far as it can tell, you might as well have deleted it. > the current state of affairs is _perfectly_ usable, reasonably > understandable and consistent and fit for release. 1000% agreement.