summaryrefslogtreecommitdiff
path: root/lispref/nonascii.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2006-05-30 04:31:02 +0000
committerRichard M. Stallman <rms@gnu.org>2006-05-30 04:31:02 +0000
commit19bce67e970e80602a1697853effa1b0dc46ad74 (patch)
tree6632ce1a8f5f8b931bf0d587c03b88c5594f04e1 /lispref/nonascii.texi
parentd1fe296738025966e64a4708628e6a4596601086 (diff)
downloademacs-19bce67e970e80602a1697853effa1b0dc46ad74.tar.gz
(Default Coding Systems): Further clarification.
Diffstat (limited to 'lispref/nonascii.texi')
-rw-r--r--lispref/nonascii.texi11
1 files changed, 5 insertions, 6 deletions
diff --git a/lispref/nonascii.texi b/lispref/nonascii.texi
index f36cda3b7b5..2224fdbd436 100644
--- a/lispref/nonascii.texi
+++ b/lispref/nonascii.texi
@@ -1123,12 +1123,11 @@ If @var{operation} is @code{insert-file-contents}, the argument
corresponding to the target may be a cons cell of the form
@code{(@var{filename} . @var{buffer})}). In that case, @var{filename}
is a file name to look up in @code{file-coding-system-alist}, and
-@var{buffer} is a buffer will contain the file's contents (not yet
-decoded). If the file's association in
-@code{file-coding-system-alist} specifies a function to call, and that
-function needs to examine the file's contents (as it usually does), it
-should examine the contents of @var{buffer} instead of reading the
-file.
+@var{buffer} is a buffer that contains the file's contents (not yet
+decoded). If @code{file-coding-system-alist} specifies a function to
+call for this file, and that function needs to examine the file's
+contents (as it usually does), it should examine the contents of
+@var{buffer} instead of reading the file.
@end defun
@node Specifying Coding Systems