summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2002-08-15 20:30:32 +0000
committerRichard M. Stallman <rms@gnu.org>2002-08-15 20:30:32 +0000
commitddb0de6969fd973561ad7bf73aa68e432be987e3 (patch)
treeba53da6f7aca0027b8de5901a7f7d7c650573d07 /man
parent48241cb53f9aed148c125cac70d950d7432075a4 (diff)
downloademacs-ddb0de6969fd973561ad7bf73aa68e432be987e3.tar.gz
Explain how C-x RET f and C-x RET c affect saving.
Diffstat (limited to 'man')
-rw-r--r--man/mule.texi36
1 files changed, 20 insertions, 16 deletions
diff --git a/man/mule.texi b/man/mule.texi
index 06bb9617166..6c401417703 100644
--- a/man/mule.texi
+++ b/man/mule.texi
@@ -896,8 +896,8 @@ system, you can use these commands to specify one:
@table @kbd
@item C-x @key{RET} f @var{coding} @key{RET}
-Use coding system @var{coding} for the visited file
-in the current buffer.
+Use coding system @var{coding} for saving or revisiting the visited
+file in the current buffer.
@item C-x @key{RET} c @var{coding} @key{RET}
Specify coding system @var{coding} for the immediately following
@@ -924,12 +924,14 @@ selection---the next one---to or from the window system.
@kindex C-x RET f
@findex set-buffer-file-coding-system
- The command @kbd{C-x @key{RET} f} (@code{set-buffer-file-coding-system})
-specifies the file coding system for the current buffer---in other
-words, which coding system to use when saving or rereading the visited
-file. You specify which coding system using the minibuffer. Since this
-command applies to a file you have already visited, it affects only the
-way the file is saved.
+ The command @kbd{C-x @key{RET} f}
+(@code{set-buffer-file-coding-system}) sets the file coding system for
+the current buffer---in other words, it says which coding system to
+use when saving or reverting the visited file. You specify which
+coding system using the minibuffer. If you specify a coding system
+that cannot handle all of the characters in the buffer, Emacs warns
+you about the troublesome characters when you actually save the
+buffer.
@kindex C-x RET c
@findex universal-coding-system-argument
@@ -942,17 +944,19 @@ command}.
So if the immediately following command is @kbd{C-x C-f}, for example,
it reads the file using that coding system (and records the coding
-system for when the file is saved). Or if the immediately following
+system for when you later save the file). Or if the immediately following
command is @kbd{C-x C-w}, it writes the file using that coding system.
-Other file commands affected by a specified coding system include
-@kbd{C-x C-i} and @kbd{C-x C-v}, as well as the other-window variants of
-@kbd{C-x C-f}.
+When you specify the coding system for saving in this way, instead
+of with @kbd{C-x @key{RET} f}, there is no warning if the buffer
+contains characters that the coding system cannot handle.
- @kbd{C-x @key{RET} c} also affects commands that start subprocesses,
-including @kbd{M-x shell} (@pxref{Shell}).
+ Other file commands affected by a specified coding system include
+@kbd{C-x C-i} and @kbd{C-x C-v}, as well as the other-window variants
+of @kbd{C-x C-f}. @kbd{C-x @key{RET} c} also affects commands that
+start subprocesses, including @kbd{M-x shell} (@pxref{Shell}).
- However, if the immediately following command does not use the coding
-system, then @kbd{C-x @key{RET} c} ultimately has no effect.
+ If the immediately following command does not use the coding system,
+then @kbd{C-x @key{RET} c} ultimately has no effect.
An easy way to visit a file with no conversion is with the @kbd{M-x
find-file-literally} command. @xref{Visiting}.