Re: package.el encoding problem

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> > Can you enable "Options => Enter Debugger on Quit", then reproduce the
>> > problem then hit C-g when you get the prompt?
>> > [ Or do `M-: (debug)` when you get the prompt.  ]
>> Don't bother I managed to reproduce it after all.  It should fixed, thanks,
> Thanks, but I don't think I understand the fix.

As you can see in the fix's assertion, the data we receive is
a unibyte string and we need to save it into a file.

We used to put it into a multibyte buffer, which then causes the save
the be all confused because the bytes 128-255 it contains aren't part of
any coding-system.  We did try to circumvent this problem by specifying
`no-conversion` coding system, but I think the way we did this wasn't
quite right.

Rather than try to fix the circumvention, I decided to "do it right" and
use a unibyte buffer so the question doesn't show up.

> I thought the need for unibyte buffers was removed long ago, at least
> in the vast majority of situations.

It is definitely *possible* to use multibyte buffers even in cases where
we only manipulate bytes, but it is undesirable.


        Stefan