[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_30.ht
From: |
Patrice Dumas |
Subject: |
[Texi2html-cvs] Changes to texi2html/Tests/xemacs_frame_res/xemacs_30.html |
Date: |
Tue, 23 Aug 2005 19:52:45 -0400 |
Index: texi2html/Tests/xemacs_frame_res/xemacs_30.html
diff -u texi2html/Tests/xemacs_frame_res/xemacs_30.html:1.22
texi2html/Tests/xemacs_frame_res/xemacs_30.html:1.23
--- texi2html/Tests/xemacs_frame_res/xemacs_30.html:1.22 Tue Aug 9
17:19:26 2005
+++ texi2html/Tests/xemacs_frame_res/xemacs_30.html Tue Aug 23 23:51:17 2005
@@ -188,11 +188,11 @@
<p> Lisp allows any variable to have any kind of value, but most variables
that Emacs uses require a value of a certain type. Often the value has
to be a string or a number. Sometimes we say that a certain feature is
-turned on if a variable is "non-<code>nil</code>," meaning that if
the
+turned on if a variable is “non-<code>nil</code>,” meaning that if
the
variable's value is <code>nil</code>, the feature is off, but the feature is
on for <i>any</i> other value. The conventional value to turn on the
-feature--since you have to pick one particular value when you set the
-variable--is <code>t</code>.
+feature—since you have to pick one particular value when you set the
+variable—is <code>t</code>.
</p>
<p> Emacs uses many Lisp variables for internal recordkeeping, as any Lisp
program must, but the most interesting variables for you are the ones that
@@ -497,7 +497,7 @@
<p> Some options have a small fixed set of possible legitimate values.
These options don't let you edit the value textually. Instead, an
active field <samp>`[Value Menu]'</samp> appears before the value; invoke this
-field to edit the value. For a boolean "on or off" value, the active
+field to edit the value. For a boolean “on or off” value, the
active
field says <samp>`[Toggle]'</samp>, and it changes to the other value.
<samp>`[Value Menu]'</samp> and <samp>`[Toggle]'</samp> edit the buffer; the
changes
take effect when you use the <samp>`Set for Current Session'</samp> operation.
@@ -527,8 +527,8 @@
</p>
<p> You can also invoke <samp>`[Current dir?]'</samp> to switch between
including
a specific named directory in the path, and including <code>nil</code> in the
-path. (<code>nil</code> in a search path means "try the current
-directory.")
+path. (<code>nil</code> in a search path means “try the current
+directory.”)
</p>
<a name="IDX1483"></a>
<a name="IDX1484"></a>
@@ -590,7 +590,7 @@
</pre></td></tr></table>
<p>Invoking <samp>`[Done]'</samp> buries this customization buffer. Each of
the
-other fields performs an operation--set, save or reset--on each of the
+other fields performs an operation—set, save or reset—on each of
the
items in the buffer that could meaningfully be set, saved or reset.
</p>
<hr size="6">
@@ -706,7 +706,7 @@
<p> If you want to alter a particular user option variable with the
customization buffer, and you know its name, you can use the command
<kbd>M-x customize-option</kbd> and specify the option name. This sets up
-the customization buffer with just one option--the one that you asked
+the customization buffer with just one option—the one that you asked
for. Editing, setting and saving the value work as described above, but
only for the specified option.
</p>
@@ -959,7 +959,7 @@
If you do not need to disguise the local variables list as a comment in
this way, there is no need to include a prefix or a suffix.
</p>
-<p> Two "variable" names are special in a local variables list: a
value
+<p> Two “variable” names are special in a local variables list: a
value
for the variable <code>mode</code> sets the major mode, and a value for the
variable <code>eval</code> is simply evaluated as an expression and the value
is ignored. These are not real variables; setting them in any other
@@ -1794,7 +1794,7 @@
table (though sometimes related major modes use the same one) which it
installs in each buffer that uses that major mode. The syntax table
installed in the current buffer is the one that all commands use, so we
-call it "the" syntax table. A syntax table is a Lisp object, a
vector of
+call it “the” syntax table. A syntax table is a Lisp object, a
vector of
length 256 whose elements are numbers.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -3358,7 +3358,7 @@
command if it is typed while Emacs is waiting for input.
</p>
<p>If you quit twice in a row before the first <kbd>C-g</kbd> is recognized,
you
-activate the "emergency escape" feature and return to the shell.
+activate the “emergency escape” feature and return to the shell.
See section <a href="#SEC398">Emergency Escape</a>.
</p>
<a name="IDX1553"></a>
@@ -3376,7 +3376,7 @@
the debugger.
</p>
<a name="IDX1558"></a>
-<p> The command <kbd>M-x top-level</kbd> is equivalent to "enough"
<kbd>C-]</kbd>
+<p> The command <kbd>M-x top-level</kbd> is equivalent to
“enough” <kbd>C-]</kbd>
commands to get you out of all the levels of recursive edits that you are
in. <kbd>C-]</kbd> only gets you out one level at a time, but <kbd>M-x
top-level</kbd>
goes out all levels at once. Both <kbd>C-]</kbd> and <kbd>M-x top-level</kbd>
are
@@ -3422,7 +3422,7 @@
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC397">27.12.4 Spontaneous Entry
to Incremental Search</a></td><td> </td><td align="left"
valign="top"> Spontaneous entry to incremental search.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC398">27.12.5 Emergency
Escape</a></td><td> </td><td align="left" valign="top"> Emergency
escape--
+<tr><td align="left" valign="top"><a href="#SEC398">27.12.5 Emergency
Escape</a></td><td> </td><td align="left" valign="top"> Emergency
escape—
What to do if Emacs stops responding.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC399">27.12.6 Help for Total
Frustration</a></td><td> </td><td align="left" valign="top"> When
you are at your wits' end.
@@ -3552,7 +3552,7 @@
<p> If Emacs spontaneously displays <samp>`I-search:'</samp> at the bottom of
the
screen, it means that the terminal is sending <kbd>C-s</kbd> and <kbd>C-q</kbd>
-according to the poorly designed xon/xoff "flow control" protocol.
You
+according to the poorly designed xon/xoff “flow control” protocol.
You
should try to prevent this by putting the terminal in a mode where it will
not use flow control, or by giving it enough padding that it will never send a
<kbd>C-s</kbd>. If that cannot be done, you must tell Emacs to expect flow
@@ -3704,7 +3704,7 @@
<p> If Emacs executes an illegal instruction, or dies with an operating
system error message that indicates a problem in the program (as opposed to
-something like "disk full"), then it is certainly a bug.
+something like “disk full”), then it is certainly a bug.
</p>
<p> If Emacs updates the display in a way that does not correspond to what is
in the buffer, then it is certainly a bug. If a command seems to do the
@@ -3786,11 +3786,11 @@
facts and nothing but the facts.
</p>
<p> Do not assume that the problem is due to the size of the file and say,
-"When I visit a large file, Emacs prints out <samp>`I feel pretty
today'</samp>."
-This is what we mean by "guessing explanations". The problem is
just as
+“When I visit a large file, Emacs prints out <samp>`I feel pretty
today'</samp>.”
+This is what we mean by “guessing explanations”. The problem is
just as
likely to be due to the fact that there is a <samp>`z'</samp> in the file
name. If
this is so, then when we got your report, we would try out the problem with
-some "large file", probably with no <samp>`z'</samp> in its name,
and not find
+some “large file”, probably with no <samp>`z'</samp> in its name,
and not find
anything wrong. There is no way in the world that we could guess that we
should try visiting a file with a <samp>`z'</samp> in its name.
</p>
@@ -3801,10 +3801,10 @@
command previously? This is why we ask you to give the exact sequence of
characters you typed since starting to use Emacs.
</p>
-<p> You should not even say "visit a file" instead of <kbd>C-x
C-f</kbd> unless
+<p> You should not even say “visit a file” instead of <kbd>C-x
C-f</kbd> unless
you <i>know</i> that it makes no difference which visiting command is used.
-Similarly, rather than saying "if I have three characters on the
line,"
-say "after I type <kbd><kbd>RET</kbd> A B C <kbd>RET</kbd>
C-p</kbd>," if that is
+Similarly, rather than saying “if I have three characters on the
line,”
+say “after I type <kbd><kbd>RET</kbd> A B C <kbd>RET</kbd>
C-p</kbd>,” if that is
the way you entered the text.
</p>
<p> If you are not in Fundamental mode when the problem occurs, you should