On 2010-10-25, Richard Heck wrote:
> On 10/25/2010 01:23 PM, John McCabe-Dansted wrote:
>> On Tue, Oct 26, 2010 at 12:03 AM, Richard Heck<rgh...@comcast.net> wrote:
>>>> + e.checksum() != s.checksum()) {
>>>> There are a number of ways to get a dirty buffer without actually
>>>> changing the file. E.g we can add two spaces that get converted to a
>>>> single space, or we can add a character and then remove it by
>>>> backspacing. This seems to happen fairly regularly to me, so it seems
>>>> worth checking for.
>>> I'm not sure where this code is. I'd want to see the context before deciding
>>> whether this is worth it.
>> It occurs immediately prior to prompting the user whether we want to
>> open the original or the emergency file. I consider it worthwhile
>> since even IO is cheap compared to user time (and user concentration).
> OK. Does anyone else have a view about this?
I'd like this test also before the "save buffer?" popup when closing LyX.
(Currently, even "<change-something>; undo" will trigger this prompt.)
Günter
