[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Texi2html-cvs] Changes to texi2html/Tests/xemacs_frame_res/xemacs_12.ht
From: |
Patrice Dumas |
Subject: |
[Texi2html-cvs] Changes to texi2html/Tests/xemacs_frame_res/xemacs_12.html |
Date: |
Tue, 23 Aug 2005 19:52:41 -0400 |
Index: texi2html/Tests/xemacs_frame_res/xemacs_12.html
diff -u texi2html/Tests/xemacs_frame_res/xemacs_12.html:1.20
texi2html/Tests/xemacs_frame_res/xemacs_12.html:1.21
--- texi2html/Tests/xemacs_frame_res/xemacs_12.html:1.20 Tue Aug 9
17:19:25 2005
+++ texi2html/Tests/xemacs_frame_res/xemacs_12.html Tue Aug 23 23:51:16 2005
@@ -106,7 +106,7 @@
</p>
<p> Many commands that insert text, such as <kbd>C-y</kbd>
(<code>yank</code>) and
<kbd>M-x insert-buffer</kbd>, position the mark at one end of the inserted
-text--the opposite end from where point is positioned, so that the region
+text—the opposite end from where point is positioned, so that the region
contains the text just inserted.
</p>
<p> Aside from delimiting the region, the mark is useful for marking
@@ -693,7 +693,7 @@
<p> The most basic delete commands are <kbd>C-d</kbd>
(<code>delete-char</code>) and
<kbd>DEL</kbd> (<code>delete-backward-char</code>). <kbd>C-d</kbd> deletes the
-character after point, the one the cursor is "on top of". Point
+character after point, the one the cursor is “on top of”. Point
doesn't move. <kbd>DEL</kbd> deletes the character before the cursor, and
moves point back. You can delete newlines like any other characters in
the buffer; deleting a newline joins two lines. Actually, <kbd>C-d</kbd> and
@@ -864,7 +864,7 @@
<h2 class="section"> 9.5 Yanking </h2>
<p> <em>Yanking</em> means getting back text which was killed. Some systems
-call this "pasting". The usual way to move or copy text is to kill
it
+call this “pasting”. The usual way to move or copy text is to
kill it
and then yank it one or more times.
</p>
<dl compact="compact">
@@ -936,14 +936,14 @@
<p> <kbd>C-u C-y</kbd> yanks the text, leaves the cursor in front of the text,
and sets the mark after it, if the argument is with just a <kbd>C-u</kbd>.
Any other argument, including <kbd>C-u</kbd> and digits, has different
-results, described below, under "Yanking Earlier Kills".
+results, described below, under “Yanking Earlier Kills”.
</p>
<a name="IDX336"></a>
<a name="IDX337"></a>
<p> To copy a block of text, you can also use <kbd>M-w</kbd>
(<code>copy-region-as-kill</code>), which copies the region into the kill ring
without removing it from the buffer. <kbd>M-w</kbd> is similar to
<kbd>C-w</kbd>
-followed by <kbd>C-y</kbd> but does not mark the buffer as
"modified" and
+followed by <kbd>C-y</kbd> but does not mark the buffer as
“modified” and
does not actually cut anything.
</p>
<hr size="6">
@@ -993,7 +993,7 @@
followed it, and the second <kbd>C-k</kbd> kills the newline after the second
line. The result is that the buffer contains <samp>`This is and here is the
third.'</samp> and a single kill entry contains <samp>`the
first<kbd>RET</kbd>line of
-sample text<kbd>RET</kbd>'</samp>--all the killed text, in its original order.
+sample text<kbd>RET</kbd>'</samp>—all the killed text, in its original
order.
</p>
<a name="IDX338"></a>
<a name="IDX339"></a>
@@ -1035,22 +1035,22 @@
the last kill, then <kbd>M-y</kbd> to replace it with the previous
kill.
</p>
-<p> You can think in terms of a "last yank" pointer which points at
an item
-in the kill ring. Each time you kill, the "last yank" pointer moves
to
+<p> You can think in terms of a “last yank” pointer which points
at an item
+in the kill ring. Each time you kill, the “last yank” pointer
moves to
the new item at the front of the ring. <kbd>C-y</kbd> yanks the item
-which the "last yank" pointer points to. <kbd>M-y</kbd> moves the
"last
-yank" pointer to a different item, and the text in the buffer changes to
+which the “last yank” pointer points to. <kbd>M-y</kbd> moves the
“last
+yank” pointer to a different item, and the text in the buffer changes to
match. Enough <kbd>M-y</kbd> commands can move the pointer to any item in the
ring, so you can get any item into the buffer. Eventually the pointer
reaches the end of the ring; the next <kbd>M-y</kbd> moves it to the first item
again.
</p>
-<p> Yanking moves the "last yank" pointer around the ring, but does
not
+<p> Yanking moves the “last yank” pointer around the ring, but
does not
change the order of the entries in the ring, which always runs from the
most recent kill at the front to the oldest one still remembered.
</p>
-<p> Use <kbd>M-y</kbd> with a numeric argument to advance the "last
-yank" pointer by the specified number of items. A negative argument
+<p> Use <kbd>M-y</kbd> with a numeric argument to advance the “last
+yank” pointer by the specified number of items. A negative argument
moves the pointer toward the front of the ring; from the front of the
ring, it moves to the last entry and starts moving forward from there.
</p>
@@ -1058,7 +1058,7 @@
stop doing <kbd>M-y</kbd> commands and the text will stay there. Since the
text is just a copy of the kill ring item, editing it in the buffer does
not change what's in the ring. As long you don't kill additional text,
-the "last yank" pointer remains at the same place in the kill ring:
+the “last yank” pointer remains at the same place in the kill ring:
repeating <kbd>C-y</kbd> will yank another copy of the same old kill.
</p>
<p> If you know how many <kbd>M-y</kbd> commands it would take to find the
@@ -1067,8 +1067,8 @@
restores the text the specified number of entries back in the kill
ring. Thus, <kbd>C-u 2 C-y</kbd> gets the next to the last block of killed
text. It is equivalent to <kbd>C-y M-y</kbd>. <kbd>C-y</kbd> with a numeric
-argument starts counting from the "last yank" pointer, and sets the
-"last yank" pointer to the entry that it yanks.
+argument starts counting from the “last yank” pointer, and sets the
+“last yank” pointer to the entry that it yanks.
</p>
<a name="IDX340"></a>
<p> The variable <code>kill-ring-max</code> controls the length of the kill
@@ -1354,7 +1354,7 @@
<li>
Commands that operate on the region only work if the region is active.
</li><li>
-Only a very small set of commands causes the region to become active--
+Only a very small set of commands causes the region to become active—
those commands whose semantics are to mark an area, such as
<code>mark-defun</code>.
</li><li>
The region is deactivated after each command that is executed, except that
@@ -1401,7 +1401,7 @@
<p>When <code>zmacs-regions</code> is <code>t</code>, programs can be
non-intrusive
on the state of the region by setting the variable
<code>zmacs-region-stays</code>
to a non-<code>nil</code> value. If you are writing a new Emacs command that
-is conceptually a "motion" command and should not interfere with the
+is conceptually a “motion” command and should not interfere with
the
current highlightedness of the region, then you may set this variable.
It is reset to <code>nil</code> after each user command is executed.
</p>
@@ -1544,7 +1544,7 @@
</p></dd>
<dt> <kbd>M-x kill-rectangle</kbd></dt>
<dd><p>Similar, but also save the contents of the region-rectangle as the
-"last killed rectangle".
+“last killed rectangle”.
</p></dd>
<dt> <kbd>M-x yank-rectangle</kbd></dt>
<dd><p>Yank the last killed rectangle with its upper left corner at point.
@@ -1564,13 +1564,13 @@
<a name="IDX345"></a>
<a name="IDX346"></a>
<p> There are two ways to get rid of the text in a rectangle: you can discard
-the text (delete it) or save it as the "last killed" rectangle. The
+the text (delete it) or save it as the “last killed” rectangle.
The
commands for these two ways are <kbd>M-x delete-rectangle</kbd> and <kbd>M-x
kill-rectangle</kbd>. 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 move left.
</p>
-<p> Note that "killing" a rectangle is not killing in the usual
sense; the
+<p> 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
only records the most recently killed rectangle (that is, does not
append to a killed rectangle). Different yank commands