Re: master e8488bcc9c: Avoid having font locking triggering unnecessary auto-saving

[Stefan Monnier]

Lars Ingebrigtsen [2022-05-11 13:22:46] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> I'm actually not quite sure what the semantics should be if the buffer
>>> is buffer-modified-p => nil and we're called with
>>> (restore-buffer-modified-p 'autosaved)...
>>
>> (restore-buffer-modified-p 'autosaved) can be done by doing
>> the same as what happens if you do (restore-buffer-modified-p
>> 'autosaved) and then you wait for auto-save to kick in, no?
>
> Uhm...  I don't follow.  If somebody does
> (restore-buffer-modified-p 'autosaved), then that buffer won't be
> autosaved...  (Well, until the user modifies the buffer.)

I'm saying that there should be no difficulty making
(restore-buffer-modified-p 'autosaved) do the right thing since
(restore-buffer-modified-p t) followed by auto-saving gives us the
resulting state (of <FOO>_MODIFF vars) we want: we just need to mimic
the behavior of that sequence of calls (but without performing the
auto-save itself, of course).


        Stefan