Subject: Re: bug#13949: 24.4.1; `fill-paragraph' should not always put the buffer as modified

From: Dmitry Gutov <[email-masked]>
Date: Sun, 27 Mar 2016 18:42:43 +0300

On 03/27/2016 06:28 PM, Óscar Fuentes wrote:

> The docs say:
>
>
>   This shows two dashes (‘--’) if the buffer displayed in the window has
>   the same contents as the corresponding file on the disk; i.e., if the
>   buffer is unmodified.

That might be a documentation bug. Switch to an unmodified buffer. Type 
`a', and then backspace. What do you see in the status?

> AFAIK, a file-visiting buffer is not marked as modified when text
> properties are applied to it.

It is. If you're thinking of font-lock, then it uses 
with-silent-modifications.