Maybe I spoke too soon, maybe that's a new problem.
Here's another recipe, that will (at least most of the time) cause a
change of the buffer-modified flag.
1. start emacs -Q
2. in scratch buffer evaluate the following 2 expressions
(setq ediff-split-window-function 'split-window-horizontally)
(se
> "Stefan" == Stefan Monnier <[EMAIL PROTECTED]> writes:
Stefan>
>>> Can you send a reproducible test case?
Stefan>
>> This is due to the recent changes to font-lock. The problem goes away
>> if you turn global-font-lock-mode off. The buffer is modified or not,
>> de
>> When I do an isearch with todays CVS version, sometimes the modified
>> flag of the buffer gets set.
>> Can you send a reproducible test case?
> This is due to the recent changes to font-lock. The problem goes away if you
> turn global-font-lock-mode off. The buffer is modified or not, depend
> When I do an isearch with todays CVS version, sometimes the modified
> flag of the buffer gets set.
>
> Can you send a reproducible test case?
This is due to the recent changes to font-lock. The problem goes away if you
turn global-font-lock-mode off. The buffer is modified or not
When I do an isearch with todays CVS version, sometimes the modified flag
of the buffer gets set.
Can you send a reproducible test case?
I've tried M-x debug-on-entry for
set-buffer-modified-p
and restore-buffer-modified-p, but they didn't get
It would be
When I do an isearch with todays CVS version, sometimes the modified flag
of the buffer gets set. I've tried M-x debug-on-entry for set-buffer-modified-p
and restore-buffer-modified-p, but they didn't get hit (at least not when
the modified flag changed suddenly during isearch).
I could also observ
