Re: Invalid output to process

[Kim F. Storm]

Milan Zamazal <address@hidden> writes:

>
> ... "\236                                       "

This part is a unibyte string.

>

          ...

Now, transmitting that unibyte string converted \236 + space into NUL.

Somebody (not me) can probably explain why that happens when coding
system is raw-text-unix but not with no-conversion.

>
> But if I use
>
>   (set-process-coding-system process 'no-conversion 'no-conversion)
>
> instead of
>
>   (set-process-coding-system process 'raw-text-unix 'raw-text-unix)
>
> after opening the process in bug2.el, the input is correct:
>
>
> ž         ...

Now, this is a multibyte string.

but they are still EQUAL:

Try this:

(setq mb "ž                                       ")
=> "ž                                       "

(setq ub (string-as-unibyte mb))
=> "\236                                       "

(equal mb ub)
=> t


I suppose you can make a much simpler test case by sending either mb
or ub through your process.


-- 
Kim F. Storm <address@hidden> http://www.cua.dk