@item
The variable @code{show-trailing-whitespace} has no special meaning, so
trailing whitespace on a line is now always displayed correctly: as
-empty space. To see if a line ends with spaces or TABs, type @kbd{C-e}
+empty space. To see if a line ends with spaces or tabs, type @kbd{C-e}
on that line. Likewise, empty lines at the end of the buffer are not
marked in any way; use @kbd{M->} to see where the end of the buffer is.
@findex toggle-hungry-state (c-)
@findex toggle-auto-state (c-)
@findex toggle-auto-hungry-state (c-)
-@ccmode{} provides keybindings which allow you to toggle the minor
+@ccmode{} provides key bindings which allow you to toggle the minor
modes on the fly while editing code. To toggle just the auto-newline
state, hit @kbd{C-c C-a} (@code{c-toggle-auto-state}). When you do
this, you should see the @samp{a} indicator either appear or disappear
@findex set-offset (c-)
You can use the command @kbd{C-c C-o} (@code{c-set-offset}) as the way
to set offsets, both interactively and from your mode
-hook@footnote{Obviously, you use the keybinding interactively, and the
+hook@footnote{Obviously, you use the key binding interactively, and the
function call programmatically!}.
@vindex c-basic-offset
indent-tabs-mode nil)
;; we like auto-newline and hungry-delete
(c-toggle-auto-hungry-state 1)
- ;; keybindings for all supported languages. We can put these in
+ ;; key bindings for all supported languages. We can put these in
;; c-mode-base-map because c-mode-map, c++-mode-map, objc-mode-map,
;; java-mode-map, idl-mode-map, and pike-mode-map inherit from it.
(define-key c-mode-base-map "\C-m" 'c-context-line-break)
foreground (the first character) and the background (the second
character) colors of the default face. Each character should be the
hexadecimal code for the desired color on a standard PC text-mode
-display. For example, to get blue text on a lightgray backgraound,
+display. For example, to get blue text on a light gray background,
specify @samp{EMACSCOLORS=17}, since 1 is the code of the blue color and
-7 is the code of the lightgray color.
+7 is the code of the light gray color.
The PC display usually supports only eight background colors. However,
Emacs switches the DOS display to a mode where all 16 colors can be used
@ignore
@item @code{privateColormap} (class @code{PrivateColormap})
-If @samp{on}, use a private colormap, in the case where the ``default
+If @samp{on}, use a private color map, in the case where the ``default
visual'' of class PseudoColor and Emacs is using it.
@end ignore
line. You can customize @code{display-time-mail-face} to make the mail
indicator prominent.
-@cindex mode line, 3D appearence
+@cindex mode line, 3D appearance
@cindex attributes of mode line, changing
@cindex non-integral number of lines in a window
By default, the mode line is drawn on graphics displays with
* Select Buffer:: Creating a new buffer or reselecting an old one.
* List Buffers:: Getting a list of buffers that exist.
-* Misc Buffer:: Renaming; changing read-onlyness; copying text.
+* Misc Buffer:: Renaming; changing read-onliness; copying text.
* Kill Buffer:: Killing buffers you no longer need.
* Several Buffers:: How to go through the list of all buffers
and operate variously on several of them.
It is often used as an enhanced email address book.
-EUDC considers BBDB as a directory server backend just like LDAP or
-PH/QI servers though BBDB has no client/server protocol and thus always
+EUDC considers BBDB as a directory server back end just like LDAP or
+PH/QI servers, though BBDB has no client/server protocol and thus always
resides locally on your machine. The point in this is not to offer an
alternate way to query your BBDB database (BBDB itself provides much
-more flexible ways to do that) but rather to offer an interface to your
+more flexible ways to do that), but rather to offer an interface to your
local directory that is consistent with the interface to external
directories (LDAP, PH/QI). This is particularly interesting when
performing queries on multiple servers.
* Display of Query Results:: Controlling how query results are presented
* Inline Query Expansion:: How to use and customize inline queries
* The Server Hotlist:: How to use and manage the server hotlist
-* Multi-server Queries:: How to query multiple servers sucessively
+* Multi-server Queries:: How to query multiple servers successively
* Creating BBDB Records:: How to insert query results into your BBDB
* Server/Protocol Locals:: Customizing on a per server/protocol basis
@end menu
server. You will not need this unless your server runs on a port other
than the default (which depends on the protocol).
If the directory server resides on your own computer (which is the case
-if you use the BBDB backend) then `localhost' is a reasonable value but
+if you use the BBDB back end) then `localhost' is a reasonable value but
it will be ignored anyway.
@end defvar
@defvar eudc-duplicate-attribute-handling-method
A method to handle entries containing duplicate attributes. This is
-either an alist @code{(@var{attr} . @var{method})} or a symbol
+either an alist of elements @code{(@var{attr} . @var{method})}, or a symbol
@var{method}. The alist form of the variable associates a method to an
-individual attribute name, the second form specifies a method applicable
+individual attribute name; the second form specifies a method applicable
to all attribute names. Available methods are: @code{list},
-@code{first}, @code{concat}, @code{duplicate} (see above). Defaults to
+@code{first}, @code{concat}, and @code{duplicate} (see above). The default is
@code{list}.
@end defvar
Attributes}).
The display of each individual field can be performed by an arbitrary
-function which allows specific processing for binary values like images
-or audio samples as well as values with computer semantics like URLs.
+function which allows specific processing for binary values, such as
+images or audio samples, as well as values with semantics, such as
+URLs.
@defvar eudc-attribute-display-method-alist
An alist specifying methods to display attribute values. Each member of
The hotlist edit buffer offers a means to manage a list of frequently
used servers. Commands are available in the context pop-up menu
generally bound to the right mouse button. Those commands also have
-equivalent keybindings.
+equivalent key bindings.
@deffn Command eudc-hotlist-add-server
Bound to @kbd{a}.
directory server. You do this by moving point to the appropriate
record in a query result display buffer and invoking the command
@kbd{M-x eudc-insert-record-at-point-into-bbdb} with the
-keyboard binding @kbd{b} @footnote{This keybinding does not actually
+keyboard binding @kbd{b} @footnote{This key binding does not actually
call @code{eudc-insert-record-at-point-into-bbdb} but uses
@code{eudc-try-bbdb-insert} instead.}, or with the menu. EUDC
cannot update an existing BBDB record and will signal an error if you
@end defun
The following functions allow you to set the value of a variable with
-various degrees of localness.
+various degrees of locality.
@defun eudc-default-set var val
Set the EUDC default value of @var{var} to @var{val}.
* Menu Bars:: Enabling and disabling the menu bar.
* Tool Bars:: Enabling and disabling the tool bar.
* Dialog Boxes:: Controlling use of dialog boxes.
-* Tooltips:: Showing "tooltips", AKA "ballon help" for active text.
+* Tooltips:: Showing "tooltips", AKA "balloon help" for active text.
* Mouse Avoidance:: Moving the mouse pointer out of the way.
* Non-Window Terminals:: Multiple frames on terminals that show only one.
* XTerm Mouse:: Using the mouse in an XTerm terminal emulator.
Expert users often turn off the menu bar, especially on text-only
terminals, where this makes one additional line available for text.
If the menu bar is off, you can still pop up a menu of its contents
-with @kbd{C-Mouse-3} on a display which supports popup menus.
+with @kbd{C-Mouse-3} on a display which supports pop-up menus.
@xref{Menu Mouse Clicks}.
@xref{Menu Bar}, for information on how to invoke commands with the
@table @code
@item banish
-Move the mouse to the upper-right corner on any keypress;
+Move the mouse to the upper-right corner on any key-press;
@item exile
Move the mouse to the corner only if the cursor gets too close,
and allow it to return once the cursor is out of the way;
in the file.
@item
-In Fortran code, functions, subroutines and blockdata are tags.
+In Fortran code, functions, subroutines and block data are tags.
@item
In makefiles, targets are tags.
You can specify a regular expression for a particular language, by
writing @samp{@{lang@}} in front of it. Then @code{etags} will use
the regular expression only for files of that language. (@samp{etags
---help} prints the list of languages recognised by @code{etags}.) The
+--help} prints the list of languages recognized by @code{etags}.) The
following example tags the @code{DEFVAR} macros in the Emacs source
files, for the C language only:
* Viewing Cross-References:: Who references or cites what?
* RefTeXs Menu:: The Ref menu in the menubar.
-* Keybindings:: The default keybindings.
+* Key Bindings:: The default key bindings.
* Faces:: Fontification of RefTeX's buffers.
* Multifile Documents:: Document spread over many files.
* Language Support:: How to support other languages.
@chapter All the Rest
@end iftex
-@node RefTeXs Menu, Keybindings, Viewing Cross-References, Top
+@node RefTeXs Menu, Key Bindings, Viewing Cross-References, Top
@section @b{Ref@TeX{}}'s Menu
@cindex RefTeXs Menu
@cindex Menu, in the menu bar
@code{Customize} submenu which can be used to access @b{Ref@TeX{}}'s
entire set of options.@refill
-@node Keybindings, Faces, RefTeXs Menu, Top
-@section Default Keybindings
-@cindex Keybindings, summary
+@node Key Bindings, Faces, RefTeXs Menu, Top
+@section Default Key Bindings
+@cindex Key Bindings, summary
-Here is a summary of the available keybindings.
+Here is a summary of the available key bindings.
@kindex C-c =
@kindex C-c (
@c FIXME: Do we need bindings for the Index macros here as well?
@c C-c i C-c I or so????
-@c How about keybindings for reftex-reset-mode and reftex-parse-document?
+@c How about key bindings for reftex-reset-mode and reftex-parse-document?
@kindex C-c t
@kindex C-c l
@kindex C-c r
@end example
@noindent These keys are reserved for the user, so I cannot bind them by
-default. If you want to have these keybindings available, set in your
+default. If you want to have these key bindings available, set in your
@file{.emacs} file:
@vindex reftex-extra-bindings
@end lisp
@vindex reftex-load-hook
-Changing and adding to @b{Ref@TeX{}}'s keybindings is best done in the hook
+Changing and adding to @b{Ref@TeX{}}'s key bindings is best done in the hook
@code{reftex-load-hook}. For information on the keymaps
which should be used to add keys, see @ref{Keymaps and Hooks}.
-@node Faces, AUCTeX, Keybindings, Top
+@node Faces, AUCTeX, Key Bindings, Top
@section Faces
@cindex Faces
@item
@b{Viper mode}@*
@cindex Viper mode
-@cindex Keybindings, problems with Viper mode
+@cindex Key bindings, problems with Viper mode
@findex viper-harness-minor-mode
With @i{Viper} mode prior to Vipers version 3.01, you need to protect
@b{Ref@TeX{}}'s keymaps with@refill
Here is a summary of @b{Ref@TeX{}}'s commands which can be executed from
LaTeX files. Command which are executed from the special buffers are
not described here. All commands are available from the @code{Ref}
-menu. For keybindings, @pxref{Keybindings}.
+menu. See @xref{Key Bindings}.
@deffn Command reftex-toc
Show the table of contents for the current document. When called with
@defopt reftex-extra-bindings
Non-@code{nil} means, make additional key bindings on startup. These
extra bindings are located in the users @samp{C-c letter}
-map. @xref{Keybindings}.@refill
+map. @xref{Key Bindings}.@refill
@end defopt
@defopt reftex-plug-into-AUCTeX
@itemize @bullet
@item
New option @code{reftex-toc-max-level} to limit the depth of the toc.
-New keybinding @kbd{t} in the @file{*toc*} buffer to change this
+New key binding @kbd{t} in the @file{*toc*} buffer to change this
setting.@refill
@item
RefTeX maintaines an @file{Index Phrases} file in which phrases can be
into the reply buffer's keymap. Instead, it puts its commands on a
keymap prefix, then installs this prefix onto the buffer's keymap. What
this means is that you typically have to type more characters to invoke
-a Supercite command, but Supercite's keybindings can be made much more
+a Supercite command, but Supercite's key bindings can be made much more
consistent across MUAs.
You can control what key Supercite uses as its keymap prefix by changing
the variable @code{sc-mode-map-prefix}. By default, this variable is
set to @code{C-c C-p}; a finger twister perhaps, but unfortunately the
-best default due to the scarcity of available keybindings in many MUAs.
+best default due to the scarcity of available key bindings in many MUAs.
@item
@emph{Turns on Supercite minor mode.}
\input texinfo @c -*-texinfo-*-
@c
-@c $Id: speedbar.texi,v 1.7 2001/02/17 17:02:12 rms Exp $
+@c $Id: speedbar.texi,v 1.8 2001/08/20 01:19:13 rms Exp $
@c
@c This file is part of GNU Emacs
to use.
@menu
-* Basic Keybindings::
+* Basic Key Bindings::
* Basic Visuals::
* Mouse Bindings::
* Displays Submenu::
@end menu
-@node Basic Keybindings, Basic Visuals, Basic Navigation, Basic Navigation
+@node Basic Key Bindings, Basic Visuals, Basic Navigation, Basic Navigation
@comment node-name, next, previous, up
-@section Basic Keybindings
-@cindex keybindings
+@section Basic Key Bindings
+@cindex key bindings
-These keybindings are common across all modes:
+These key bindings are common across all modes:
@table @kbd
@item delete, SPC
Contract the current group, hiding sub items.
@end table
-@node Basic Visuals, Mouse Bindings, Basic Keybindings, Basic Navigation
+@node Basic Visuals, Mouse Bindings, Basic Key Bindings, Basic Navigation
@comment node-name, next, previous, up
@section Basic Visuals
@cindex visuals
In all modes, a group can be `edited' by pressing @kbd{RET}, meaning a
file will be opened, or a directory explicitly opened in speedbar. A
group can be expanded or contracted using @kbd{+} or
-@kbd{-}. @xref{Basic Keybindings}.
+@kbd{-}. @xref{Basic Key Bindings}.
Sometimes groups may have a @samp{?} in its indicator box. This means
that it is a group type, but there are no contents, or no known way of
@menu
* Directory Display:: What the display means.
* Hidden Files:: How to display hidden files.
-* File Keybindings:: Performing file operations.
+* File Key Bindings:: Performing file operations.
@end menu
@node Directory Display, Hidden Files, File Mode, File Mode
indicating that all symbols which alphabetically fall between those
categories are included in that sub-group. @xref{Tag Hierarchy Methods}.
-@node Hidden Files, File Keybindings, Directory Display, File Mode
+@node Hidden Files, File Key Bindings, Directory Display, File Mode
@comment node-name, next, previous, up
@section Hidden Files
@cindex hidden files
determine their presence by the @samp{#} and @samp{!} file indicators.
@xref{Directory Display}.
-@node File Keybindings, , Hidden Files, File Mode
+@node File Key Bindings, , Hidden Files, File Mode
@comment node-name, next, previous, up
-@section File Keybindings
-@cindex file keybindings
+@section File Key Bindings
+@cindex file key bindings
-File mode has keybindings permitting different file system operations
+File mode has key bindings permitting different file system operations
such as copy or rename. These commands all operate on the @dfn{current
file}. In this case, the current file is the file at point, or clicked
on when pulling up the menu.
and uses the same unknown file indicator (@pxref{File Mode}).
Buffer mode does not have file operation bindings, but the following
-buffer specific keybindings are available:
+buffer specific key bindings are available:
@table @kbd
@item k
will override any major display mode currently being displayed for the
duration of the specialized buffer's use. Minor display modes
will follow the general rules of their major counterparts in terms of
-keybindings and visuals, but will have specialized behaviors.
+key bindings and visuals, but will have specialized behaviors.
@menu
* RMAIL:: Managing folders in speedbar
@cindex @code{speedbar-reconfigure-keymaps-hook}
@item speedbar-reconfigure-keymaps-hook
Hooks run when the keymaps are regenerated. Keymaps are reconfigured
-whenever modes change. This will let you add custom keybindings.
+whenever modes change. This will let you add custom key bindings.
@cindex @code{speedbar-before-popup-hook}
@item speedbar-before-popup-hook
Hooks called before popping up the speedbar frame.
@printindex cp
@bye
-@c LocalWords: speedbar's xref Keybindings slowbar kbd subsubsection
+@c LocalWords: speedbar's xref slowbar kbd subsubsection
@c LocalWords: keybindings
cursor on it and use @kbd{C-c C-z} again. This exposes the level-2 body
and its level-3 child subheadings and narrows the buffer again. Zooming
in on successive subheadings can be done as much as you like. A string
-in the modeline shows how deep you've gone.
+in the mode line shows how deep you've gone.
When zooming in on a heading, to see only the child subheadings specify
a numeric argument: @kbd{C-u C-c C-z}. The number of levels of children
can be specified too (compare @kbd{M-x show-children}), e.g.@: @kbd{M-2
C-c C-z} exposes two levels of child subheadings. Alternatively, the
-body can be spcified with a negative argument: @kbd{M-- C-c C-z}. The
+body can be specified with a negative argument: @kbd{M-- C-c C-z}. The
whole subtree can be expanded, similarly to @kbd{C-c C-s} (@kbd{M-x
show-subtree}), by specifying a zero argument: @kbd{M-0 C-c C-z}.
@vindex tex-start-options-string
The value of the variable @code{tex-start-options-string} specifies
options for the @TeX{} run. The default value causes @TeX{} to run in
-nonstopmode. To run @TeX{} interactively, set the variable to @code{""}.
+nonstop mode. To run @TeX{} interactively, set the variable to @code{""}.
@vindex tex-main-file
Large @TeX{} documents are often split into several files---one main
@item Insert state
Insert state is the Vi insertion mode. @key{ESC} will take you back to
Vi state. Insert state editing can be done, including auto-indentation. By
-default, Viper disables Emacs keybindings in Insert state.
+default, Viper disables Emacs key bindings in Insert state.
@item Replace state
Commands like @kbd{cw} invoke the Replace state. When you cross the
help with key bindings for the major mode of that buffer).
If you switch to Vi in Dired or similar modes---no harm is done. It is just
-that the special keybindings provided by those modes will be temporarily
+that the special key bindings provided by those modes will be temporarily
overshadowed by Viper's bindings. Switching back to Viper's Emacs state
will revive the environment provided by the current major mode.
@menu
* Rudimentary Changes:: Simple constant definitions.
-* Keybindings:: Enabling Emacs Keys, Rebinding keys, etc.
+* Key Bindings:: Enabling Emacs Keys, Rebinding keys, etc.
* Packages that Change Keymaps:: How to deal with such beasts.
* Viper Specials:: Special Viper commands.
* Vi Macros:: How to do Vi style macros.
@end menu
-@node Rudimentary Changes,Keybindings,Customization,Customization
+@node Rudimentary Changes,Key Bindings,Customization,Customization
@section Rudimentary Changes
@cindex setting variables
@vindex @code{viper-replace-state-hook}
@vindex @code{viper-emacs-state-hook}
-@node Keybindings, Packages that Change Keymaps, Rudimentary Changes,Customization
-@section Keybindings
+@node Key Bindings, Packages that Change Keymaps, Rudimentary Changes,Customization
+@section Key Bindings
-@cindex keybindings
+@cindex key bindings
@cindex keymaps
Viper lets you define hot keys, i.e., you can associate keyboard keys
@findex @code{viper-add-local-keys}
@findex @code{viper-zap-local-keys}
-@node Packages that Change Keymaps,Viper Specials,Keybindings,Customization
+@node Packages that Change Keymaps,Viper Specials,Key Bindings,Customization
@subsection Packages that Change Keymaps
@cindex C-c and Viper
@cindex Viper and C-c
This is very useful if you run out of function keys on your keyboard; it
makes Viper macro facility a @emph{keyboard doubler}, so to speak.
-Elsewhere (@xref{Keybindings}, for details), we review
+Elsewhere (@xref{Key Bindings}, for details), we review
the standard Emacs mechanism for binding function keys to commands.
For instance,
@node Mapping, Shell Commands, File and Buffer Handling, Commands
@section Mapping
-@cindex keybindings
+@cindex key bindings
@cindex key mapping
@table @kbd