(Decoding Output): Document that null bytes force no-conversion for reading

process output.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 5ce7a42ec1c08692baaa22e8019174ffb9f96020..a2b4b87d5e5f268cef55897d5cfc7e24d071ac2b 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,5 +1,11 @@
 2009-01-10  Eli Zaretskii  <eliz@gnu.org>
 
+       * 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 265e63b6deed46f32ee477b79065db38020e316d..ae3246f0d291d1b0125a37c3ea59ac050a5f3a9b 100644 (file)
--- 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