|INFOKEY(1)||General Commands Manual||INFOKEY(1)|
infokey — compile
custom key bindings file
infokey utility compiles a source file
by default) containing info(1) customizations into a binary format ($HOME/.info
by default). info(1) reads the binary file at startup to override the default key bindings and variable definitions.
Besides the standard
--version options, the only option is
--output file. This tells
infokey to write the binary data to
file instead of
#info j next-line k prev-line l forward-char h backward-char \kd next-line \ku prev-line \kr forward-char \kl backward-char \ scroll-forward \kD scroll-forward-page-only b scroll-backward \kU scroll-backward-page-only g beginning-of-node \kh beginning-of-node G end-of-node \ke end-of-node \t select-reference-this-line - history-node n next-node p prev-node u up-node t top-node d dir-node #var scroll-step=1
The source file consists of one or more "sections". Each section starts with a line that identifies the type of section. Possible sections are:
STRING whitespace ACTION [ whitespace [ # comment ] ] newline
Whitespace is any sequence of one or more spaces and/or tabs. Comment is any sequence of any characters, excluding newline.
STRING is the key sequence which invokes the action. ACTION is the name of an info(1) command. The characters in STRING are interpreted literally or prefixed by a caret (`^') to indicate a control character. A backslash followed by certain characters specifies input keystrokes as follows:
Backslash followed by any other character indicates that character is to be taken literally. Characters which must be preceded by a backslash include caret, space, tab, and backslash itself.
Blank lines and lines starting with `#' are ignored, except for the special section header lines.
Key bindings defined in the .info
file take precedence over info's default key bindings, whether or not
--vi-keys is used. A default key binding may be
disabled by overriding it in the .info file with the
action `invalid'. In addition,
all default key
bindings can be disabled by adding this line
in the relevant section:
This will cause info(1) to ignore all the default key commands for that section.
Beware: `#stop' can be dangerous. Since it disables all default key bindings, you must supply enough new key bindings to enable all necessary actions. Failure to bind any key to the `quit' command, for example, can lead to frustration.
The order in which key bindings are defined in the .info file is not important, except that the command summary produced by the `get-help-window' command only displays the first key that is bound to each command.
|February 15, 2003||OpenBSD-current|