Re: Don't complain about changed file when it hasn't changed

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Date: Tue, 30 Aug 2016 11:44:54 -0400
> 
> >> >  . the file's buffer could be unibyte, in which case you want
> >> >    insert-file-contents-literally, I think
> >> We could try to be more careful in this way, indeed.  But AFAIK the only
> >> risk here is to flag a file as being changed when it hasn't, which is no
> >> worse than what we currently do (i.e. a false alarm), so I'm not sure
> >> it's worth the trouble.
> > The documentation should state this exemption, lest users expect
> > unibyte buffers to get the same treatment.
> 
> I don't know for a fact that it doesn't work in the unibyte case, actually.

buffer-file-coding-system will be the local default, so a non-ASCII
file will be decoded.