| [Top] | [Contents] | [Index] | [ ? ] |
This manual describes PCL-CVS, the GNU Emacs front-end to CVS. It is nowhere near complete, so you are advised to use M-x customize-group RET pcl-cvs RET and to look at the documentation strings of the various commands and major modes for further information.
1. About PCL-CVS Installation, credits, history, ...
2. Getting started An introduction with a walk-through example. 3. Buffer contents An explanation of the buffer contents. 4. Selected files To which files are commands applied. 5. Commands All commands, grouped by type.
6. Editing a Log Message Major mode to edit log messages. 7. Browsing a Log of Changes Major mode to browse log changes. 8. Customization How you can tailor PCL-CVS to suit your needs. 9. Bugs (known and unknown)
Function and Variable Index List of functions and variables. Concept Index List of concepts. Key Index List of keystrokes.
-- The Detailed Node Listing ---
About PCL-CVS
1.1 Contributors to PCL-CVS 1.2 Installation
Commands
5.1 Entering PCL-CVS Commands to invoke PCL-CVS 5.2 Setting flags for CVS commands 5.3 Updating the `*cvs*' buffer 5.4 Movement Commands How to move up and down in the buffer 5.5 Marking files How to mark files that other commands will later operate on. 5.6 Committing changes Checking in your modifications to the CVS repository. 5.7 Editing files Loading files into Emacs. 5.8 Getting info about files Display the log and status of files. 5.9 Adding and removing files 5.10 Undoing changes 5.11 Removing handled entries Uninteresting lines can easily be removed. 5.12 Ignoring files Telling CVS to ignore generated files. 5.13 Viewing differences Commands to `diff' different versions. 5.14 Running ediff Running `ediff' from `*cvs*' buffer. 5.15 Updating files Updating files that Need-update. 5.16 Tagging files 5.17 Miscellaneous commands
Customization
8.1 Customizing Faces
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
PCL-CVS is a front-end to CVS versions 1.9 and later. It concisely shows the present status of a checked out module in an Emacs buffer and provides single-key access to the most frequently used CVS commands. For Emacs users accustomed to VC, PCL-CVS can be thought of as a replacement for VC-dired (see section `Dired under VC' in The GNU Emacs Manual) specifically designed for CVS.
PCL-CVS was originally written many years ago by Per Cederqvist who proudly maintained it until January 1996, at which point he released the beta version 2.0b2 and passed on the maintainership to Greg A Woods. Development stayed mostly dormant for a few years during which version 2.0 never seemed to be able to leave the "beta" stage while a separate XEmacs version was slowly splitting away. In late 1998, Stefan Monnier picked up development again, adding some major new functionality and taking over the maintenance.
As of Emacs 21, PCL-CVS is part of the standard Emacs distribution.
1.1 Contributors to PCL-CVS 1.2 Installation
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Contributions to the package are welcome. I have limited time to work on this project, but I will gladly add any code that you contribute to me to this package (see section 9. Bugs (known and unknown)).
The following persons have made contributions to PCL-CVS.
cvs-status-mode.
Apart from these, a lot of people have sent us suggestions, ideas, requests, bug reports and encouragement. Thanks a lot! Without you there would be no new releases of PCL-CVS.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
As mentioned above, PCL-CVS comes bundled with Emacs version 21.1 and later. If you're using Emacs 20, you can download an older version of PCL-CVS from ftp://flint.cs.yale.edu/pub/monnier/pcl-cvs. That version also works on XEmacs.
If you are running XEmacs 21.0 or later, PCL-CVS is available in pre-compiled package form. Please refer to the XEmacs manual for instructions regarding package selection and installation. Currently, that PCL-CVS package also requires you to have installed the `xemacs-base', `elib', and `dired' packages.
If you have TeX installed at your site, you can make a typeset manual from `pcl-cvs.texi'.
dvi2ps, which does. There
is also a program which comes together with TeX, dvips, which
you can use.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document assumes that you know what CVS is, and that you at least know the fundamental concepts of CVS. If that is not the case, you should read the CVS documentation. Type info -f cvs or man cvs.
PCL-CVS is only useful once you have checked out a module. So before you invoke it, you must have a copy of a module somewhere in the file system.
You can invoke PCL-CVS by typing M-x cvs-examine RET. You can also invoke it via the menu bar, under `Tools'. Or, if you prefer, you can also invoke PCL-CVS by simply visiting the CVS administrative subdirectory of your module, with a prefix argument. For example, to invoke PCL-CVS in a separate frame, type C-u C-x 5 f ~/my/project/CVS RET.
The function cvs-examine will ask for a directory. The command
`cvs -n update' will be run in that directory. (It should contain
files that have been checked out from a CVS archive.) The output from
cvs will be parsed and presented in a table in a buffer called
`*cvs*'. It might look something like this:
Repository : /usr/CVSroot
Module : test
Working dir: /users/ceder/FOO/test
In directory .:
Need-Update bar
Need-Update file.txt
Modified namechange
Need-Update newer
In directory sub:
Modified ChangeLog
--------------------- End ---------------------
-- last cmd: cvs -f -z6 -n update -d -P --
|
In this example, your repository is in `/usr/CVSroot' and CVS has been run in the directory `/users/ceder/FOO/test'. The three files (`bar', `file.txt' and `newer') that are marked with `Need-Update' have been changed by someone else in the CVS repository. Two files (`namechange' and `sub/ChangeLog') have been modified locally, and need to be checked in.
You can move the cursor up and down in the buffer with C-n and C-p or n and p. If you press c on one of the `Modified' files, that file will be checked in to the CVS repository. See section 5.6 Committing changes. You can also press O to update any of the files that are marked `Need-Update'. You can also run M-x cvs-update RET (bound to M-u in the `*cvs*' buffer) to update all the files.
You can then press = to easily get a `diff' between your modified file and the base version that you started from, or you can press l to get the output from `cvs log'. Many more such commands are available simply by pressing a key (see section 5.8 Getting info about files).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The display contains several columns, some of which are optional. These columns are, from left to right:
The `file status' field can have the following values:
rcsmerge command on
the two versions; an unmodified copy of your file is also in your
working directory, with the name `.#file.version',
where version is the RCS revision that your modified file started
from. See section 5.13 Viewing differences, for more details.A conflict can also come from a disagreement on the existence of the file rather than on its content. This case is indicated by the following possible substatus:
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Many of the commands work on the current set of selected files which can be either the set of marked files (if any file is marked and marks are no ignored) or whichever file or directory the cursor is on.
If a directory is selected but the command cannot be applied to a directory, then it will be applied to the set of files under this directory which are in the `*cvs*' buffer.
Furthermore, each command only operates on a subset of the selected
files, depending on whether or not the command is applicable to
each file (based on the file's status). For example,
cvs-mode-commit is not applicable to a file whose status is
`Need-Update'. If it should happen that PCL-CVS guesses the
applicability wrong, you can override it with the special prefix
cvs-mode-force-command normally bound to M-f (and file a
bug report). The applicability rule can be slightly changed with
cvs-allow-dir-commit and cvs-force-dir-tag.
By default, marks are always in effect (you may change this, however, by
setting the variable cvs-default-ignore-marks) except for the
commands that `tag' or `diff' a file (which can be changed
with the variable cvs-invert-ignore-marks).
In addition, you may use the special prefix cvs-mode-toggle-marks
normally bound to T to toggle the use of marks for the following
command.
This scheme might seem a little complicated, but once one gets used to it, it is quite powerful.
For commands to mark and unmark files, see 5.5 Marking files.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The nodes in this menu contains explanations about all the commands that you can use in PCL-CVS. They are grouped together by type.
5.1 Entering PCL-CVS Commands to invoke PCL-CVS 5.2 Setting flags for CVS commands 5.3 Updating the `*cvs*' buffer 5.4 Movement Commands How to move up and down in the buffer 5.5 Marking files How to mark files that other commands will later operate on. 5.6 Committing changes Checking in your modifications to the CVS repository. 5.7 Editing files Loading files into Emacs. 5.8 Getting info about files Display the log and status of files. 5.9 Adding and removing files 5.10 Undoing changes 5.11 Removing handled entries Uninteresting lines can easily be removed. 5.12 Ignoring files Telling CVS to ignore generated files. 5.13 Viewing differences Commands to `diff' different versions. 5.14 Running ediff Running `ediff' from `*cvs*' buffer. 5.15 Updating files Updating files that Need-update. 5.16 Tagging files 5.17 Miscellaneous commands
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Most commands in PCL-CVS require that you have a `*cvs*' buffer. The commands that you use to get one are listed below. For each, a `cvs' process will be run, the output will be parsed by PCL-CVS, and the result will be printed in the `*cvs*' buffer (see 3. Buffer contents, for a description of the buffer's contents).
cvs-examine except that it does
not access the CVS repository, which is a major advantage when the
repository is far away. But of course, it will not be able to detect
when a file needs to be updated or merged.
The first four of
those commands are also reachable from the menu bar
under `Tools->PCL-CVS'. Finally, an alternative way is to visit
the CVS administrative subdirectory in your work area with a simple
prefix argument. For example C-u C-x C-f ~/my/work/CVS RET. This
by default runs cvs-quickdir but the specific behavior can be
changed with cvs-dired-action and cvs-dired-use-hook.
By default, the commands above will descend recursively into subdirectories. You can avoid that behavior by including `-l' in the flags for the command. These flags can be set by giving a prefix argument to the command (e.g., by typing C-u M-x cvs-update RET -l RET).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section describes the convention used by nearly all PCL-CVS commands for setting optional flags sent to CVS. A single C-u prefix argument is used to cause the command to prompt for flags to be used for the current invocation of the command only. Two C-u prefix arguments are used to prompt for flags which will be set permanently, for the current invocation and all that follow, until the flags are changed, or unless temporary flags are set which override them.
Perhaps an example or two is in order. Say you are about to add a binary file to the repository, and want to specify the flags `-kb' to `cvs add'. You can type C-u a -kb RET, enter the description, and the file will be added. Subsequent `cvs add' commands will use the previously prevailing flags.
As a second example, say you are about to perform a diff and want to see
the result in unified diff format, i.e. you'd like to pass the flag
`-u' to both `cvs diff' and `diff'. You'd also like all
subsequent diffs to use this flag. You can type C-u C-u = -u RET
and the diff will be performed, and the default flags will be set to
("-u"). You can of course override this flag for a single diff
by using a single C-u prefix argument.
In addition to this, some commands can take special prefix arguments. These work as follows: When called with a C-u prefix, the user is prompted for a new value of the special prefix and the special prefix is activated for the next command. When called without the C-u prefix, the special prefix is re-activated (with the same value as last time) for the next command. Calling the prefix command again when it's already activated deactivates it. Calling it with the C-u C-u prefix activates it for all subsequent commands until you deactivate it explicitly. The special prefixes are:
cvs-mode-diff or to cvs-mode-update.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following commands can be used from within the `*cvs*' buffer to update the display:
In addition to the above commands which operate on the whole module, you can run the equivalent CVS command on just a subset of the files/directories with these keys:
cvs-mode-update on the selected files. When run on the
top-level directory, this is equivalent to M-u.
cvs-mode-examine on the selected files. When run on the
top-level directory, this is equivalent to M-e.cvs-mode-status on the selected files. When run on the
top-level directory, this is equivalent to M-s, except that
CVS output will be shown in a `*cvs-info*' buffer that will be
put in `cvs-status-mode'.| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can use most normal Emacs commands to move forward and backward in the buffer. Some keys are rebound to functions that take advantage of the fact that the buffer is a PCL-CVS buffer:
cvs-mode-next-line).
cvs-mode-previous-line).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
PCL-CVS works on a set of selected files (see section 4. Selected files). You can mark and unmark files with these commands:
cvs-mode-mark).
cvs-mode-unmark).
cvs-mode-mark-all-files).
cvs-mode-unmark-all-files).
cvs-mode-unmark-up).
cvs-mode-mark-matching-files).
cvs-mode-toggle-marks).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Committing changes basically works as follows:
There's no hidden state, so you can abort the process or pick it up again at any time.
The set of files actually committed is really decided only during the
very last step, which is a mixed blessing. It allows you to go back and
change your mind about which files to commit, but it also means that you
might inadvertently change the set of selected files. To reduce the
risk of error, C-c C-c will ask for confirmation if the set of
selected files has changed between the first step and the last. You can
change this last detail with log-edit-confirm.
As for the difference between c (i.e. cvs-mode-commit) and
C (i.e. cvs-mode-commit-setup) is that the first gets you
straight to `*cvs-commit*' without erasing it or changing anything
to its content, while the second first erases `*cvs-commit*'
and tries to initialize it with a sane default (it does that by either
using a template provided by the CVS administrator or by extracting a
relevant log message from a `ChangeLog' file).
If you are editing the files in your Emacs, an automatic `revert-buffer' will be performed. (If the file contains `$Id$' keywords, `cvs commit' will write a new file with the new values substituted. The auto-revert makes sure that you get them into your buffer). The revert will not occur if you have modified your buffer, or if `cvs-auto-revert' is set to `nil'.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are currently three commands that can be used to find a file (that is, load it into a buffer and start editing it there). These commands work on the line that the cursor is situated at. They always ignore any marked files.
cvs-mode-find-file). If
the cursor points to a directory, run dired on that directory;
See Info file `emacs', node `Dired'.
cvs-mode-find-file-other-window).
cvs-mode-add-change-log-entry-other-window).| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
cvs-mode-log which runs `cvs log' on all
selected files, and show the result in a temporary buffer
`*cvs-info*' (see section 7. Browsing a Log of Changes).
cvs-mode-status which runs `cvs status' on
all selected files, and show the result in a temporary buffer
`*cvs-info*'.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following commands are available to make it easy to add fuiles to and remove them from the CVS repository.
This command can also be used on `Removed' files (before you commit them) to resurrect them.
The command that is run is cvs-mode-add.
The command that is run is cvs-mode-remove-file.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
cvs-mode-undo-local-changes.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
x invokes cvs-mode-remove-handled. If
`cvs-auto-remove-handled' is set to non-nil, this will
automatically be performed after every commit.
cvs-mode-acknowledge).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The `.cvsignore' file should normally be added to the repository, but you could ignore it as well, if you like it better that way.
This runs cvs-mode-ignore.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
cvs-mode-diff).
With the d b command you can run a `diff' on the files `.#file.version' and `file'.
cvs-mode-diff-head).
cvs-mode-diff-vendor).
By default, `diff' commands ignore the marks. This can be changed
with cvs-invert-ignore-marks.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ediff (or emerge, depending on
`cvs-idiff-imerge-handlers') to allow you to view diffs.
If a prefix argument is given, PCL-CVS will prompt for a revision against
which the diff should be made, else the default will be to use the BASE
revision.
ediff (or emerge, see above) to allow you
to do an interactive 3-way merge.
Note: When the file status is `Conflict', CVS has already performed a merge. The resulting file is not used in any way if you use this command. If you use the q command inside `ediff' (to successfully terminate a merge) the file that CVS created will be overwritten.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
cvs-mode-update).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
cvs-mode-tag). It's usually preferable to tag a directory
at a time. Rather than selecting all files (which too often doesn't
select all files but only the few that are displayed), clear the
selection with M-DEL (cvs-mode-unmark-all-files), position
the cursor on the directory you want to tag and hit t.
By default, `tag' commands ignore the marks. This can be changed
with cvs-invert-ignore-marks. Also, by default `tag' can
only be applied to directories, see cvs-force-dir-tag if you want
to change this behavior.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can only use this command when a message in the `*cvs*' buffer tells
you so. You should wait a while before using this command in case
someone else is running a cvs command.
Also note that this only works if the repository is local.
cvs-help).
cvs-mode-quit).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Buffers for entering/editing log messages for changes which are about to be committed are put into Log Edit mode.
Sometimes the log buffer contains default text when you enter it, typically the last log message entered. If it does, mark and point are set around the entire contents of the buffer so that it is easy to kill the contents of the buffer with C-w.
If you work by writing entries in the `ChangeLog' (@xref{(emacs)Change Log}) and then commit the change under revision control, you can generate the Log Edit text from the ChangeLog using C-a C-a (log-edit-insert-changelog). This looks for entries for the file(s) concerned in the top entry in the ChangeLog and uses those paragraphs as the log text. This text is only inserted if the top entry was made under your user name on the current date. @xref{(emacs)Change Logs and VC}, for the opposite way of working--generating ChangeLog entries from the revision control log.
In the Log Edit buffer, C-c C-f (M-x log-edit-show-files) shows the list of files to be committed in case you need to check that.
When you have finished editing the log message, type C-c C-c to exit the buffer and commit the change.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Log View mode provides a few useful commands for navigating revision
control log output. It is used for the output buffers of both
cvs-mode-log and vc-print-log.
In this mode, n goes to the next message and p goes to the previous message and N and P go to the next and previous files, respectively, in multi-file output. With a numeric prefix argument, these commands move that many messages of files.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you have an idea about any customization that would be handy but isn't present in this list, please tell me! For info on how to reach me, see 9. Bugs (known and unknown).
nil value,
`cvs-mode-remove-handled' will be called every time you check in
files, after the check-in is ready. See section 5.11 Removing handled entries.
nil value, directories that do
not contain any files to be checked in will not be listed in the
`*cvs*' buffer.
cvs(5)). This regexp
is used to search for the last line in that output. It is normally set
to `$'. That setting is only correct if the command outputs
nothing. Note that PCL-CVS will get very confused if the command
outputs anything to stderr.
cvs command is run, it
will be called as `cvs -d cvs-cvsroot...'. This can be
useful if your site has several repositories.
nil, include full `ChangeLog'
paragraphs in the CVS log created by `cvs-mode-changelog-commit'.
This may be set in the local variables section of a `ChangeLog'
file, to indicate the policy for that `ChangeLog'.
A `ChangeLog' paragraph is a bunch of log text containing no blank lines; a paragraph usually describes a set of changes with a single purpose, but perhaps spanning several functions in several files. Changes in different paragraphs are unrelated.
You could argue that the CVS log entry for a file should contain the
full `ChangeLog' paragraph mentioning the change to the file, even though
it may mention other files, because that gives you the full context you
need to understand the change. This is the behavior you get when this
variable is set to t, the default.
On the other hand, you could argue that the CVS log entry for a change
should contain only the text for the changes which occurred in that
file, because the CVS log is per-file. This is the behavior you get
when this variable is set to nil.
8.1 Customizing Faces
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
PCL-CVS adds a few extra features, including menus, mouse bindings, and fontification the `*cvs*' buffer. The faces defined for fontification are listed below:
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you find a bug or misfeature, don't hesitate to tell us! Send email to bug-gnu-emacs@gnu.org which is gatewayed to the newsgroup `gnu.emacs.bugs'. Feature requests should also be sent there. We prefer discussing one thing at a time. If you find several unrelated bugs, please report them separately. If you are running PCL-CVS under XEmacs, you should also send a copy of bug reports to xemacs-beta@xemacs.org.
If you have problems using PCL-CVS or other questions, send them to help-gnu-emacs@gnu.org, which is gatewayed to the `gnu.emacs.help' newsgroup. This is a good place to get help, as is cvs-info@gnu.org, gatewayed to `gnu.cvs.help'.
If you have ideas for improvements, or if you have written some extensions to this package, we would like to hear from you. We hope that you find this package useful!
Below is a partial list of currently known problems with PCL-CVS version 2.0.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This is an index of all the functions and variables documented in this manual.
| Jump to: | C L V |
|---|
| Jump to: | C L V |
|---|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This is an index of concepts discussed in this manual.
| Jump to: | *
-
.
A B C D E F G H I K L M O P Q R S T U V |
|---|
| Jump to: | *
-
.
A B C D E F G H I K L M O P Q R S T U V |
|---|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This index includes an entry for each PCL-CVS key sequence documented in this manual.
| Jump to: | %
=
?
A C D E F H I L M N O P Q R S T U X |
|---|
| Jump to: | %
=
?
A C D E F H I L M N O P Q R S T U X |
|---|
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
1. About PCL-CVS
2. Getting started
3. Buffer contents
4. Selected files
5. Commands
6. Editing a Log Message
7. Browsing a Log of Changes
8. Customization
9. Bugs (known and unknown)
Function and Variable Index
Concept Index
Key Index
| [Top] | [Contents] | [Index] | [ ? ] |
| Button | Name | Go to | From 1.2.3 go to |
|---|---|---|---|
| [ < ] | Back | previous section in reading order | 1.2.2 |
| [ > ] | Forward | next section in reading order | 1.2.4 |
| [ << ] | FastBack | previous or up-and-previous section | 1.1 |
| [ Up ] | Up | up section | 1.2 |
| [ >> ] | FastForward | next or up-and-next section | 1.3 |
| [Top] | Top | cover (top) of document | |
| [Contents] | Contents | table of contents | |
| [Index] | Index | concept index | |
| [ ? ] | About | this page |