This variable controls whether to compile the combined definition
that results from activating advice for a function.
-A value of @code{always} specifies to compile unconditionally
+A value of @code{always} specifies to compile unconditionally.
A value of @code{nil} specifies never compile the advice.
A value of @code{maybe} specifies to compile if the byte-compiler is
already loaded. A value of @code{like-original} specifies to compile
-the advice if the the original definition of the advised function is
+the advice if the original definition of the advised function is
compiled or a built-in function.
This variable takes effect only if the @var{compile} argument of
@item
For simplicity, all ASCII characters now have the same height and width.
-(Certain characters, such as Chinese characters, always have have twice
+(Certain characters, such as Chinese characters, always have twice
the standard width.) All characters are created equal.
@item
should cause auto-saving. Each time the user pauses for this long,
Emacs does auto-saving for all buffers in which that is enabled. (If
the current buffer is large, the specified timeout is multiplied by a
-factor that depends increases as the size increases; for a million-byte
+factor that increases as the size increases; for a million-byte
buffer, the factor is almost 4.)
If the value is zero or nil, then auto-saving is not done as a result
number inside of @samp{<@dots{}>}.
If the optional second argument @var{ignore} is non-@code{nil}, it
-should be buffer name in the sequence to be tried. That name will be
-considered acceptable, if it is tried, even if a buffer with that name
-exists.
+should be a string; it makes a difference if it is a name in the
+sequence of names to be tried. That name will be considered acceptable,
+if it is tried, even if a buffer with that name exists. Thus, if
+buffers named @samp{foo}, @samp{foo<2>}, @samp{foo<3>} and @samp{foo<4>}
+exist,
+
+@example
+(generate-new-buffer-name "foo")
+ @result{} "foo<5>"
+(generate-new-buffer-name "foo" "foo<3>")
+ @result{} "foo<3>"
+(generate-new-buffer-name "foo" "foo<6>")
+ @result{} "foo<5>"
+@end example
See the related function @code{generate-new-buffer} in @ref{Creating
Buffers}.
button and modifier keys. The information about the window part is kept
elsewhere in the event---in the coordinates. But
@code{read-key-sequence} translates this information into imaginary
-``prefix keys'', all of which are symbols: @code{heder-line},
+``prefix keys'', all of which are symbols: @code{header-line},
@code{horizontal-scroll-bar}, @code{menu-bar}, @code{mode-line},
@code{vertical-line}, and @code{vertical-scroll-bar}. You can define
meanings for mouse clicks in special window parts by defining key