From: Chong Yidong <cyd@stupidchicken.com>
To: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [dooglus@gmail.com: display problem after renaming open image files]
Date: Tue, 03 Apr 2007 10:03:33 -0400 [thread overview]
Message-ID: <873b3hmu6i.fsf@stupidchicken.com> (raw)
In-Reply-To: <868xd998qo.fsf@lola.quinscape.zz> (David Kastrup's message of "Tue\, 03 Apr 2007 10\:12\:47 +0200")
David Kastrup <dak@gnu.org> 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.
next prev parent reply other threads:[~2007-04-03 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 21:42 [dooglus@gmail.com: display problem after renaming open image files] Richard Stallman
2007-04-01 22:16 ` Chong Yidong
2007-04-03 7:46 ` Richard Stallman
2007-04-03 8:12 ` David Kastrup
2007-04-03 14:03 ` Chong Yidong [this message]
2007-04-05 23:13 ` Richard Stallman
2007-04-05 23:55 ` Chong Yidong
2007-04-06 17:18 ` Kim F. Storm
2007-04-07 12:41 ` Richard Stallman
2007-04-07 14:54 ` Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873b3hmu6i.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.