@c This is part of the Emacs manual.
-@c Copyright (C) 1985,86,87,93,94,95,97,00,2001 Free Software Foundation, Inc.
+@c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 2000, 2001,
+@c 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
@c See file emacs.texi for copying conditions.
-@iftex
+
+@node Killing, Yanking, Mark, Top
@chapter Killing and Moving Text
+@ifnottex
+@raisesections
+@end ifnottex
+
@dfn{Killing} means erasing text and copying it into the @dfn{kill
-ring}, from which it can be retrieved by @dfn{yanking} it. Some systems
-use the terms ``cutting'' and ``pasting'' for these operations.
-
- The commonest way of moving or copying text within Emacs is to kill it
-and later yank it elsewhere in one or more places. This is very safe
-because Emacs remembers several recent kills, not just the last one. It
-is versatile, because the many commands for killing syntactic units can
-also be used for moving those units. But there are other ways of
+ring}, from which you can bring it back into the buffer by
+@dfn{yanking} it. (Some systems use the terms ``cutting'' and
+``pasting'' for these operations.) This is the most common way of
+moving or copying text within Emacs. Killing and yanking is very safe
+because Emacs remembers several recent kills, not just the last one.
+It is versatile, because the many commands for killing syntactic units
+can also be used for moving those units. But there are other ways of
copying text for special purposes.
- Emacs has only one kill ring for all buffers, so you can kill text in
-one buffer and yank it in another buffer.
-
-@end iftex
-
-@node Killing, Yanking, Mark, Top
+@iftex
@section Deletion and Killing
+@end iftex
@cindex killing text
@cindex cutting text
@cindex deletion
Most commands which erase text from the buffer save it in the kill
-ring so that you can move or copy it to other parts of the buffer.
-These commands are known as @dfn{kill} commands. The rest of the
-commands that erase text do not save it in the kill ring; they are known
-as @dfn{delete} commands. (This distinction is made only for erasure of
-text in the buffer.) If you do a kill or delete command by mistake, you
-can use the @kbd{C-x u} (@code{undo}) command to undo it
-(@pxref{Undo}).
+ring. These commands are known as @dfn{kill} commands. The commands
+that erase text but do not save it in the kill ring are known as
+@dfn{delete} commands. The @kbd{C-x u} (@code{undo}) command
+(@pxref{Undo}) can undo both kill and delete commands; the importance
+of the kill ring is that you can also yank the text in a different
+place or places. Emacs has only one kill ring for all buffers, so you
+can kill text in one buffer and yank it in another buffer.
+
+ The delete commands include @kbd{C-d} (@code{delete-char}) and
+@key{DEL} (@code{delete-backward-char}), which delete only one
+character at a time, and those commands that delete only spaces or
+newlines. Commands that can erase significant amounts of nontrivial
+data generally do a kill operation instead. The commands' names and
+individual descriptions use the words @samp{kill} and @samp{delete} to
+say which kind of operation they perform.
@vindex kill-read-only-ok
@cindex read-only text, killing
You cannot kill read-only text, since such text does not allow any
kind of modification. But some users like to use the kill commands to
copy read-only text into the kill ring, without actually changing it.
-If you set the variable @code{kill-read-only-ok} to a non-@code{nil}
-value, the kill commands work specially in a read-only buffer: they
-move over text, and copy it to the kill ring, without actually
-deleting it from the buffer. When this happens, a message in the echo
-area tells you what is happening.
-
- The delete commands include @kbd{C-d} (@code{delete-char}) and
-@key{DEL} (@code{delete-backward-char}), which delete only one character at
-a time, and those commands that delete only spaces or newlines. Commands
-that can destroy significant amounts of nontrivial data generally kill.
-The commands' names and individual descriptions use the words @samp{kill}
-and @samp{delete} to say which they do.
-
-@cindex Delete Selection mode
-@cindex mode, Delete Selection
-@findex delete-selection-mode
- Many window systems follow the convention that insertion while text
-is selected deletes the selected text. You can make Emacs behave this
-way by enabling Delete Selection mode, with @kbd{M-x
-delete-selection-mode}, or using Custom. Another effect of this mode
-is that @key{DEL}, @kbd{C-d} and some other keys, when a selection
-exists, will kill the whole selection. It also enables Transient Mark
-mode (@pxref{Transient Mark}).
+Therefore, the kill commands work specially in a read-only buffer:
+they move over text, and copy it to the kill ring, without actually
+deleting it from the buffer. Normally, kill commands beep and display
+an error message when this happens. But if you set the variable
+@code{kill-read-only-ok} to a non-@code{nil} value, they just print a
+message in the echo area to explain why the text has not been erased.
@menu
* Deletion:: Commands for deleting small amounts of text and
blank areas.
* Killing by Lines:: How to kill entire lines of text at one time.
* Other Kill Commands:: Commands to kill large regions of text and
- syntactic units such as words and sentences.
+ syntactic units such as words and sentences.
+* Graphical Kill:: The kill ring on graphical displays:
+ yanking between applications.
@end menu
+@need 1500
@node Deletion
@subsection Deletion
-@c ??? Should be backward-delete-char
@findex delete-backward-char
@findex delete-char
+ Deletion means erasing text and not saving it in the kill ring. For
+the most part, the Emacs commands that delete text are those that
+erase just one character or only whitespace.
+
@table @kbd
@item C-d
-@itemx @key{Delete}
+@itemx @key{DELETE}
Delete next character (@code{delete-char}). If your keyboard has a
-@key{Delete} function key (usually located in the edit keypad), Emacs
+@key{DELETE} function key (usually located in the edit keypad), Emacs
binds it to @code{delete-char} as well.
@item @key{DEL}
@itemx @key{BS}
-Delete previous character (@code{delete-backward-char}). Some keyboards
-refer to this key as a ``backspace key'' and label it with a left arrow:
-@key{<-}.
+Delete previous character (@code{delete-backward-char}).
@item M-\
Delete spaces and tabs around point (@code{delete-horizontal-space}).
@item M-@key{SPC}
@kindex BACKSPACE
@kindex BS
@kindex DELETE
- Every keyboard has a large key, labeled @key{DEL}, @key{BACKSPACE},
-@key{BS} or @key{DELETE}, which is a short distance above the
+ Every keyboard has a large key which is a short distance above the
@key{RET} or @key{ENTER} key and is normally used for erasing what you
-have typed. Regardless of the actual name on the key, in Emacs it is
-equivalent to @key{DEL}---or it should be.
+have typed. It may be labeled @key{DEL}, @key{BACKSPACE}, @key{BS},
+@key{DELETE}, or even with a left arrow. Regardless of the label on
+the key, in Emacs it called @key{DEL}, and it should delete one
+character backwards.
Many keyboards (including standard PC keyboards) have a
@key{BACKSPACE} key a short ways above @key{RET} or @key{ENTER}, and a
should be.
Why do we say ``or it should be''? When Emacs starts up using a
-window system, it determines automatically which key or keys should be
-equivalent to @key{DEL}. So the @key{BACKSPACE} and/or @key{DELETE}
+graphical display, it determines automatically which key or keys should be
+equivalent to @key{DEL}. As a result, @key{BACKSPACE} and/or @key{DELETE}
keys normally do the right things. But in some unusual cases Emacs
gets the wrong information from the system. If these keys don't do
what they ought to do, you need to tell Emacs which key to use for
-@key{DEL}. @xref{DEL Gets Help}, for how to do this.
+@key{DEL}. @xref{DEL Does Not Delete}, for how to do this.
@findex normal-erase-is-backspace-mode
On most text-only terminals, Emacs cannot tell which keys the
keyboard really has, so it follows a uniform plan which may or may not
-fit your keyboard. The uniform plan is that the ASCII @key{DEL}
-character deletes, and the ASCII @key{BS} (backspace) character asks
+fit your keyboard. The uniform plan is that the @acronym{ASCII} @key{DEL}
+character deletes, and the @acronym{ASCII} @key{BS} (backspace) character asks
for help (it is the same as @kbd{C-h}). If this is not right for your
-keyboard, if you find that the key which ought to delete backwards
-enters Help instead, see @ref{DEL Gets Help}.
+keyboard, such as if you find that the key which ought to delete backwards
+enters Help instead, see @ref{DEL Does Not Delete}.
@kindex M-\
@findex delete-horizontal-space
characters before and after point. @kbd{M-@key{SPC}}
(@code{just-one-space}) does likewise but leaves a single space after
point, regardless of the number of spaces that existed previously (even
-zero).
+if there were none before). With a numeric argument @var{n}, it
+leaves @var{n} spaces after point.
@kbd{C-x C-o} (@code{delete-blank-lines}) deletes all blank lines
after the current line. If the current line is blank, it deletes all
blank lines preceding the current line as well (leaving one blank line,
-the current line).
+the current line). On a solitary blank line, it deletes that line.
@kbd{M-^} (@code{delete-indentation}) joins the current line and the
previous line, by deleting a newline and all surrounding spaces, usually
@table @kbd
@item C-k
Kill rest of line or one or more lines (@code{kill-line}).
+@item C-S-backspace
+Kill an entire line at once (@code{kill-whole-line})
@end table
@kindex C-k
When @kbd{C-k} is given a positive argument, it kills that many lines
and the newlines that follow them (however, text on the current line
-before point is spared). With a negative argument @minus{}@var{n}, it
+before point is not killed). With a negative argument @minus{}@var{n}, it
kills @var{n} lines preceding the current line (together with the text
on the current line before point). Thus, @kbd{C-u - 2 C-k} at the front
of a line kills the two previous lines.
the very beginning of a line kills the entire line including the
following newline. This variable is normally @code{nil}.
+@kindex C-S-backspace
+@findex kill-whole-line
+ @kbd{C-S-backspace} (@code{kill-whole-line}) will kill a whole line
+including its newline regardless of the position of point within the
+line. Note that many character terminals will prevent you from typing
+the key sequence @kbd{C-S-backspace}.
+
@node Other Kill Commands
@subsection Other Kill Commands
@findex kill-region
@kindex C-w
-@c DoubleWideCommands
@table @kbd
@item C-w
Kill region (from point to the mark) (@code{kill-region}).
@item M-k
Kill to end of sentence (@code{kill-sentence}).
@item C-M-k
-Kill sexp (@code{kill-sexp}). @xref{Lists}.
+Kill the following balanced expression (@code{kill-sexp}). @xref{Expressions}.
@item M-z @var{char}
Kill through the next occurrence of @var{char} (@code{zap-to-char}).
@end table
- A kill command which is very general is @kbd{C-w}
-(@code{kill-region}), which kills everything between point and the
-mark. With this command, you can kill any contiguous sequence of
-characters, if you first set the region around them.
+ The most general kill command is @kbd{C-w} (@code{kill-region}),
+which kills everything between point and the mark. With this command,
+you can kill any contiguous sequence of characters, if you first set
+the region around them.
@kindex M-z
@findex zap-to-char
numeric argument acts as a repeat count. A negative argument means to
search backward and kill text before point.
- Other syntactic units can be killed: words, with @kbd{M-@key{DEL}} and
-@kbd{M-d} (@pxref{Words}); sexps, with @kbd{C-M-k} (@pxref{Lists}); and
-sentences, with @kbd{C-x @key{DEL}} and @kbd{M-k}
-(@pxref{Sentences}).@refill
+ Other syntactic units can be killed: words, with @kbd{M-@key{DEL}}
+and @kbd{M-d} (@pxref{Words}); balanced expressions, with @kbd{C-M-k}
+(@pxref{Expressions}); and sentences, with @kbd{C-x @key{DEL}} and
+@kbd{M-k} (@pxref{Sentences}).@refill
- You can use kill commands in read-only buffers. They don't actually
-change the buffer, and they beep to warn you of that, but they do copy
-the text you tried to kill into the kill ring, so you can yank it into
-other buffers. Most of the kill commands move point across the text
-they copy in this way, so that successive kill commands build up a
-single kill ring entry as usual.
+@node Graphical Kill
+@subsection Killing on Graphical Displays
+
+ On graphical displays with window systems, the most recent kill done
+in Emacs is also the primary selection, if it is more recent than any
+selection you made in another program. This means that the paste
+commands of other window-based applications copy the text that you
+killed in Emacs. In addition, Emacs yank commands treat other
+applications' selections as part of the kill ring, so you can yank
+them into Emacs.
+
+@cindex Delete Selection mode
+@cindex mode, Delete Selection
+@findex delete-selection-mode
+ Many graphical applications follow the convention that insertion while text
+is selected deletes the selected text. You can make Emacs behave this
+way by enabling Delete Selection mode---with @kbd{M-x
+delete-selection-mode} or using Custom. Another effect of this mode
+is that @key{DEL}, @kbd{C-d} and some other keys, when a selection
+exists, will kill the whole selection. It also enables Transient Mark
+mode (@pxref{Transient Mark}).
@node Yanking, Accumulating Text, Killing, Top
@section Yanking
@dfn{Yanking} means reinserting text previously killed. This is what
some systems call ``pasting.'' The usual way to move or copy text is to
-kill it and then yank it elsewhere one or more times.
+kill it and then yank it elsewhere one or more times. This is very safe
+because Emacs remembers many recent kills, not just the last one.
@table @kbd
@item C-y
(@code{yank-pop}).
@item M-w
Save region as last killed text without actually killing it
-(@code{kill-ring-save}).
+(@code{kill-ring-save}). Some systems call this ``copying''.
@item C-M-w
Append next kill to last batch of killed text (@code{append-next-kill}).
@end table
+ On graphical displays with window systems, if there is a current
+selection in some other application, and you selected it more recently
+than you killed any text in Emacs, @kbd{C-y} copies the selection
+instead of text killed within Emacs.
+
@menu
* Kill Ring:: Where killed text is stored. Basic yanking.
* Appending Kills:: Several kills in a row all yank together.
a @kbd{C-u}, precisely. Any other sort of argument, including @kbd{C-u}
and digits, specifies an earlier kill to yank (@pxref{Earlier Kills}).
+@cindex yanking and text properties
+@vindex yank-excluded-properties
+ The yank commands discard certain text properties from the text that
+is yanked, those that might lead to annoying results. For instance,
+they discard text properties that respond to the mouse or specify key
+bindings. The variable @code{yank-excluded-properties} specifies the
+properties to discard. Yanking of register contents and rectangles
+also discard these properties.
+
@kindex M-w
@findex kill-ring-save
To copy a block of text, you can use @kbd{M-w}
with point shown by @point{}. If you type @kbd{M-d M-@key{DEL} M-d
M-@key{DEL}}, killing alternately forward and backward, you end up with
@samp{a line of sample} as one entry in the kill ring, and @samp{This
-is@ @ text.} in the buffer. (Note the double space, which you can clean
-up with @kbd{M-@key{SPC}} or @kbd{M-q}.)
+is@ @ text.} in the buffer. (Note the double space between @samp{is}
+and @samp{text}, which you can clean up with @kbd{M-@key{SPC}} or
+@kbd{M-q}.)
Another way to kill the same text is to move back two words with
@kbd{M-b M-b}, then kill all four words forward with @kbd{C-u M-d}.
text in the buffer changes to match. Enough @kbd{M-y} commands can move
the pointer to any entry in the ring, so you can get any entry into the
buffer. Eventually the pointer reaches the end of the ring; the next
-@kbd{M-y} moves it to the first entry again.
+@kbd{M-y} loops back around to the first entry again.
@kbd{M-y} moves the ``last yank'' pointer around the ring, but it does
not change the order of the entries in the ring, which always runs from
yank'' pointer remains at the same place in the kill ring, so repeating
@kbd{C-y} will yank another copy of the same previous kill.
- If you know how many @kbd{M-y} commands it would take to find the text
-you want, you can yank that text in one step using @kbd{C-y} with a
-numeric argument. @kbd{C-y} with an argument restores the text the
-specified number of entries back in the kill ring. Thus, @kbd{C-u 2
-C-y} gets the next-to-the-last block of killed text. It is equivalent
-to @kbd{C-y M-y}. @kbd{C-y} with a numeric argument starts counting
-from the ``last yank'' pointer, and sets the ``last yank'' pointer to
-the entry that it yanks.
+ If you know how many @kbd{M-y} commands it would take to find the
+text you want, you can yank that text in one step using @kbd{C-y} with
+a numeric argument. @kbd{C-y} with an argument restores the text from
+the specified kill ring entry, counting back from the most recent as
+1. Thus, @kbd{C-u 2 C-y} gets the next-to-the-last block of killed
+text---it is equivalent to @kbd{C-y M-y}. @kbd{C-y} with a numeric
+argument starts counting from the ``last yank'' pointer, and sets the
+``last yank'' pointer to the entry that it yanks.
@vindex kill-ring-max
The length of the kill ring is controlled by the variable
@cindex accumulating scattered text
Usually we copy or move text by killing it and yanking it, but there
-are other methods convenient for copying one block of text in many
+are other convenient methods for copying one block of text in many
places, or for copying many scattered blocks of text into one place. To
copy one block to many places, store it in a register
(@pxref{Registers}). Here we describe the commands to accumulate
@table @kbd
@item M-x append-to-buffer
-Append region to contents of specified buffer.
+Append region to the contents of a specified buffer.
@item M-x prepend-to-buffer
-Prepend region to contents of specified buffer.
+Prepend region to the contents of a specified buffer.
@item M-x copy-to-buffer
-Copy region into specified buffer, deleting that buffer's old contents.
+Copy region into a specified buffer, deleting that buffer's old contents.
@item M-x insert-buffer
-Insert contents of specified buffer into current buffer at point.
+Insert the contents of a specified buffer into current buffer at point.
@item M-x append-to-file
-Append region to contents of specified file, at the end.
+Append region to the contents of a specified file, at the end.
@end table
To accumulate text into a buffer, use @kbd{M-x append-to-buffer}.
@code{append-to-buffer} creates the buffer. The text is inserted
wherever point is in that buffer. If you have been using the buffer for
editing, the copied text goes into the middle of the text of the buffer,
-wherever point happens to be in it.
+starting from wherever point happens to be at that moment.
Point in that buffer is left at the end of the copied text, so
successive uses of @code{append-to-buffer} accumulate the text in the
@kbd{M-x prepend-to-buffer} is just like @code{append-to-buffer}
except that point in the other buffer is left before the copied text, so
successive prependings add text in reverse order. @kbd{M-x
-copy-to-buffer} is similar except that any existing text in the other
+copy-to-buffer} is similar, except that any existing text in the other
buffer is deleted, so the buffer is left containing just the text newly
copied into it.
- To retrieve the accumulated text from another buffer, use the command
-@kbd{M-x insert-buffer}; this too takes @var{buffername} as an argument.
-It inserts a copy of the text in buffer @var{buffername} into the
-selected buffer. You can alternatively select the other buffer for
-editing, then optionally move text from it by killing. @xref{Buffers},
-for background information on buffers.
+ To retrieve the accumulated text from another buffer, use the
+command @kbd{M-x insert-buffer}; this too takes @var{buffername} as an
+argument. It inserts a copy of the whole text in buffer
+@var{buffername} into the current buffer at point, and sets the mark
+after the inserted text. Alternatively, you can select the other
+buffer for editing, then copy text from it by killing.
+@xref{Buffers}, for background information on buffers.
Instead of accumulating text within Emacs, in a buffer, you can append
text directly into a file with @kbd{M-x append-to-file}, which takes
editing in Emacs would change the file behind Emacs's back, which
can lead to losing some of your editing.
-@node Rectangles, Registers, Accumulating Text, Top
+@node Rectangles, CUA Bindings, Accumulating Text, Top
@section Rectangles
@cindex rectangle
@cindex columns (and rectangles)
commands are useful with text in multicolumn formats, and for changing
text into or out of such formats.
+@cindex mark rectangle
When you must specify a rectangle for a command to work on, you do it
by putting the mark at one corner and point at the opposite corner. The
rectangle thus specified is called the @dfn{region-rectangle} because
-you control it in about the same way the region is controlled. But
+you control it in much the same way as the region is controlled. But
remember that a given combination of point and mark values can be
interpreted either as a region or as a rectangle, depending on the
command that uses them.
@table @kbd
@item C-x r k
-Kill the text of the region-rectangle, saving its contents as the
+Kill the text of the region-rectangle, saving its contents as the
``last killed rectangle'' (@code{kill-rectangle}).
@item C-x r d
Delete the text of the region-rectangle (@code{delete-rectangle}).
Insert blank space to fill the space of the region-rectangle
(@code{open-rectangle}). This pushes the previous contents of the
region-rectangle rightward.
-@item M-x clear-rectangle
-Clear the region-rectangle by replacing its contents with spaces.
+@item C-x r c
+Clear the region-rectangle by replacing its contents with spaces
+(@code{clear-rectangle}).
@item M-x delete-whitespace-rectangle
Delete whitespace in each of the lines on the specified rectangle,
starting from the left edge column of the rectangle.
@item C-x r t @var{string} @key{RET}
Replace rectangle contents with @var{string} on each line.
(@code{string-rectangle}).
-@item M-x replace-rectangle @key{RET} @var{string} @key{RET}
-Replaces each line of the region-rectangle with @var{string}
-(@code{string-rectangle}).
@item M-x string-insert-rectangle @key{RET} @var{string} @key{RET}
-Insert @var{STRING} on each line of the rectangle.
+Insert @var{string} on each line of the rectangle.
@end table
- The rectangle operations fall into two classes: commands deleting and
-inserting rectangles, and commands for blank rectangles.
+ The rectangle operations fall into two classes: commands for
+deleting and inserting rectangles, and commands for blank rectangles.
@kindex C-x r k
@kindex C-x r d
rectangle. The commands for these two ways are @kbd{C-x r d}
(@code{delete-rectangle}) and @kbd{C-x r k} (@code{kill-rectangle}). In
either case, the portion of each line that falls inside the rectangle's
-boundaries is deleted, causing following text (if any) on the line to
+boundaries is deleted, causing any following text on the line to
move left into the gap.
Note that ``killing'' a rectangle is not killing in the usual sense; the
rectangle is not stored in the kill ring, but in a special place that
can only record the most recent rectangle killed. This is because yanking
a rectangle is so different from yanking linear text that different yank
-commands have to be used and yank-popping is hard to make sense of.
+commands have to be used. It is hard to define yank-popping for rectangles,
+so we do not try.
@kindex C-x r y
@findex yank-rectangle
(@code{yank-rectangle}). Yanking a rectangle is the opposite of killing
one. Point specifies where to put the rectangle's upper left corner.
The rectangle's first line is inserted there, the rectangle's second
-line is inserted at a position one line vertically down, and so on. The
-number of lines affected is determined by the height of the saved
-rectangle.
+line is inserted at the same horizontal position, but one line
+vertically down, and so on. The number of lines affected is determined
+by the height of the saved rectangle.
You can convert single-column lists into double-column lists using
rectangle killing and yanking; kill the second half of the list as a
@kindex C-x r o
@findex open-rectangle
+@kindex C-x r c
@findex clear-rectangle
There are two commands you can use for making blank rectangles:
-@kbd{M-x clear-rectangle} which blanks out existing text, and @kbd{C-x r
-o} (@code{open-rectangle}) which inserts a blank rectangle. Clearing a
-rectangle is equivalent to deleting it and then inserting a blank
-rectangle of the same size.
+@kbd{C-x r c} (@code{clear-rectangle}) which blanks out existing text,
+and @kbd{C-x r o} (@code{open-rectangle}) which inserts a blank
+rectangle. Clearing a rectangle is equivalent to deleting it and then
+inserting a blank rectangle of the same size.
@findex delete-whitespace-rectangle
The command @kbd{M-x delete-whitespace-rectangle} deletes horizontal
@kindex C-x r t
@findex string-rectangle
-@findex replace-rectangle
- The command @kbd{C-x r t} (@code{M-x string-rectangle}) replaces the
+ The command @kbd{C-x r t} (@code{string-rectangle}) replaces the
contents of a region-rectangle with a string on each line. The
string's width need not be the same as the width of the rectangle. If
the string's width is less, the text after the rectangle shifts left;
rectangle shifts right.
@findex string-insert-rectangle
- The command @kbd{M-x string-insert-rectangle} is similar to
-@code{string-rectangle}, but inserts the string on each line,
+ The command @kbd{M-x string-insert-rectangle} is similar to
+@code{string-rectangle}, but inserts the string on each line,
shifting the original text to the right.
+
+@node CUA Bindings, Registers, Rectangles, Top
+@section CUA Bindings
+@findex cua-mode
+@vindex cua-mode
+@cindex CUA key bindings
+@vindex cua-enable-cua-keys
+ The command @kbd{M-x cua-mode} sets up key bindings that are
+compatible with the Common User Access (CUA) system used in many other
+applications. @kbd{C-x} means cut (kill), @kbd{C-c} copy, @kbd{C-v}
+paste (yank), and @kbd{C-z} undo. Standard Emacs commands like
+@kbd{C-x C-c} still work, because @kbd{C-x} and @kbd{C-c} only take
+effect when the mark is active (and the region is highlighted).
+However, if you don't want to override these bindings Emacs at all, set
+@code{cua-enable-cua-keys} to @code{nil}.
+
+ In CUA mode, using @kbd{Shift} together with the movement keys
+activates and highlights the region over which they move. The
+standard (unshifted) movement keys deactivate the mark, and typed text
+replaces the active region as in Delete-Selection mode
+(@pxref{Graphical Kill}).
+
+ To enter an Emacs command like @kbd{C-x C-f} while the mark is
+active, use one of the following methods: either hold @kbd{Shift}
+together with the prefix key, e.g. @kbd{S-C-x C-f}, or quickly type
+the prefix key twice, e.g. @kbd{C-x C-x C-f}.
+
+@cindex rectangle highlighting
+ CUA mode provides enhanced rectangle support with visible
+rectangle highlighting. Use @kbd{C-RET} to start a rectangle,
+extend it using the movement commands, and cut or copy it using
+@kbd{C-x} or @kbd{C-c}. @kbd{RET} moves the cursor to the next
+(clockwise) corner of the rectangle, so you can easily expand it in
+any direction. Normal text you type is inserted to the left or right
+of each line in the rectangle (on the same side as the cursor).
+
+ With CUA you can easily copy text and rectangles into and out of
+registers by providing a one-digit numeric prefix the the kill, copy,
+and yank commands, e.g. @kbd{C-1 C-c} copies the region into register
+@code{1}, and @kbd{C-2 C-v} yanks the contents of register @code{2}.
+
+@cindex global mark
+ CUA mode also has a global mark feature which allows easy moving and
+copying of text between buffers. Use @kbd{C-S-SPC} to toggle the
+global mark on and off. When the global mark is on, all text that you
+kill or copy is automatically inserted at the global mark, and text
+you type is inserted at the global mark rather than at the current
+position.
+
+ For example, to copy words from various buffers into a word list in
+a given buffer, set the global mark in the target buffer, then
+navigate to each of the words you want in the list, mark it (e.g. with
+@kbd{S-M-f}), copy it to the list with @kbd{C-c} or @kbd{M-w}, and
+insert a newline after the word in the target list by pressing
+@key{RET}.
+
+@ifnottex
+@lowersections
+@end ifnottex
+
+@ignore
+ arch-tag: d8da8f96-0928-449a-816e-ff2d3497866c
+@end ignore