From: Eli Zaretskii Date: Sat, 10 Jan 2009 12:50:38 +0000 (+0000) Subject: (Decoding Output): Document that null bytes force no-conversion for reading X-Git-Tag: emacs-pretest-23.0.90~571 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=3355f04dd806aa84cf09d7890d69971802a4bbb6;p=emacs.git (Decoding Output): Document that null bytes force no-conversion for reading process output. --- diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 5ce7a42ec1c..a2b4b87d5e5 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,5 +1,11 @@ 2009-01-10 Eli Zaretskii + * processes.texi (Decoding Output): Document that null bytes force + no-conversion for reading process output. + + * files.texi (Reading from Files): Document that null bytes force + no-conversion when visiting files. + * processes.texi (Serial Ports): Improve wording, suggested by RMS. diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi index 265e63b6dee..ae3246f0d29 100644 --- a/doc/lispref/processes.texi +++ b/doc/lispref/processes.texi @@ -1388,7 +1388,10 @@ converts the unibyte output to multibyte using system to use (@pxref{Process Information}). Otherwise, the coding system comes from @code{coding-system-for-read}, if that is non-@code{nil}; or else from the defaulting mechanism (@pxref{Default -Coding Systems}). +Coding Systems}). If the text output by a process contains null +bytes, Emacs by default uses @code{no-conversion} for it; see +@ref{Lisp and Coding Systems, inhibit-null-byte-detection}, for how to +control this behavior. @strong{Warning:} Coding systems such as @code{undecided} which determine the coding system from the data do not work entirely