Re: lisp/ChangeLog coding system

[Michael Kifer]

>     >     Michael, somehow you recoded lisp/ChangeLog with your latest change
>     >     from its specified coding system iso-2022-7bit to something else.
>     > 
>     > Michael, if you can figure out precisely how this happened, it might
>     > lead us to a way to make the Mule features more robust.  Many users
>     > might benefit from that.  So I think it is worth spending some time to
>     > try to reconstruct how this happened.
> 
>     I didn't notice any problems.
> 
> The problem was not one you would have noticed within that session.
> The problem was that the file was stored in a different coding system.
> It may not have caused inconvenience for you, but it did for others.
> So we want to track it down.
> 
> Can you please help?
> 
>     However, if there were, it is due to the fact that I had to change X
>     selection coding system to latin-1, because there is a bug in the default
>     coding system (which used to be compound-text-with-extensions, 
> 
> I don't think that specifying an X selection coding system should have
> had this result unless you copied the whole contents of ChangeLog through
> the X server.

well, the X selection thingie is the only thing that I can think of which
somehow might be related to the coding system. I just created a record in
my own change log and then copy-pasted it to the emacs changelog.
All within the same session.

I normally don't fool around with the coding system. But because there is
some kind of a bug with the default coding system for X selections, I
changed that one.  Can't think of anything else.