Re: request to revert the chnage of revno 112925

[Stefan Monnier]

>> This is not specific to Elisp, of course, it's true of most programming
>> languages
> Yes, that sounds right.  Should we make this change for all
> programming-language files then?  .c, .h, Makefile, etc....

Only for those languages that say so in the definition/standard/spec.

> True, but in practice this means one should avoid putting NUL bytes in
> such files.  grep uses a heuristic that if a file contains a NUL byte,
> it's considered to be a binary file, and by default grep won't output
> the matching lines for that file.  POSIX allows this behavior, and it's
> common among many GNU and/or POSIX tools, which means it's typically
> not a good idea to put NUL bytes in source files.

Agreed, which is why it's very rare for Elisp files to have NUL bytes.
But that's no reason to treat an Elisp file with a NUL bytes as being
encoded in binary instead of utf-8 (which is the question under
discussion here).


        Stefan