CONTENTS

SYNOPSIS

DESCRIPTION

The -V or --version option causes lesskey to print its version number and immediately exit. If -V or --version is present, other options and arguments are ignored.

The input file consists of one or more sections. Each section starts with a line that identifies the type of section. Possible sections are:

#command

If the command section is the first section in the file, this line may be omitted. The command section consists of lines of the form:

string <whitespace> action [extra-string] <newline>

Whitespace is any sequence of one or more spaces and/or tabs. The string is the command key(s) which invoke the action. The string may be a single command key, or a sequence of up to 15 keys. The action is the name of the less action, from the list below. The characters in the string may appear literally, or be prefixed by a caret to indicate a control key. A backslash followed by one to three octal digits may be used to specify a character by its octal value. A backslash followed by certain characters specifies input characters as follows:

An action may be followed by an "extra" string. When such a command is entered while running less, the action is performed, and then the extra string is parsed, just as if it were typed in to less. This feature can be used in certain cases to extend the functionality of a command. For example, see the "{" and ":t" commands in the example below. The extra string has a special meaning for the "quit" action: when less quits, first character of the extra string is used as its exit status.

#command
\r forw-line
\n forw-line
eforw-line
jforw-line
\kdforw-line
^E forw-line
^N forw-line
kback-line
yback-line
^Y back-line
^K back-line
^P back-line
Jforw-line-force
Kback-line-force
Yback-line-force
dforw-scroll
^D forw-scroll
uback-scroll
^U back-scroll
\40forw-screen
fforw-screen
^F forw-screen
^V forw-screen
\kDforw-screen
bback-screen
^B back-screen
\ev back-screen
\kUback-screen
zforw-window
wback-window
\e\40 forw-screen-force
Fforw-forever
Rrepaint-flush
rrepaint
^R repaint
^L repaint
\eu undo-hilite
ggoto-line
\khgoto-line
<goto-line
\e< goto-line
ppercent
%percent
\e[ left-scroll
\e] right-scroll
\e( left-scroll
\e) right-scroll
{forw-bracket {}
}back-bracket {}
(forw-bracket ()
)back-bracket ()
[forw-bracket []
]back-bracket []
\e^F forw-bracket
\e^B back-bracket
Ggoto-end
\e> goto-end
>goto-end
\kegoto-end
=status
^G status
:f status
/forw-search
?back-search
\e/ forw-search *
\e? back-search *
nrepeat-search
\en repeat-search-all
Nreverse-search
\eN reverse-search-all
mset-mark
’goto-mark
^X^X goto-mark
Eexamine
:e examine
^X^V examine
:n next-file
:p prev-file
tnext-tag
Tprev-tag
:x index-file
:d remove-file
-toggle-option
:t toggle-option t
stoggle-option o
_display-option
|pipe
vvisual
!shell
+firstcmd
Hhelp
hhelp
Vversion
0digit
1digit
2digit
3digit
4digit
5digit
6digit
7digit
8digit
9digit
qquit
Qquit
:q quit
:Q quit
ZZ quit

#stop

This will cause all default commands to be ignored. The #stop line should be the last line in that section of the file.

Be aware that #stop can be dangerous. Since all default commands are disabled, you must provide sufficient commands before the #stop line to enable all necessary actions. For example, failure to provide a "quit" command can lead to frustration.

#line-edit

This section specifies new key bindings for the line editing commands, in a manner similar to the way key bindings for ordinary commands are specified in the #command section. The line-editing section consists of a list of keys and actions, one per line as in the example below.

#line-edit
\t forw-complete
\17 back-complete
\e\t back-complete
^L expand
^V literal
^A literal
\el right
\kr right
\eh left
\kl left
\eb word-left
\e\kl word-left
\ew word-right
\e\kr word-right
\ei insert
\ex delete
\kx delete
\eX word-delete
\ekx word-delete
\e\b word-backspace
\e0 home
\kh home
\e$ end
\ke end
\ek up
\ku up
\ej down

#env

Following this line is a list of environment variable assignments. Each line consists of an environment variable name, an equals sign (=) and the value to be assigned to the environment variable. White space before and after the equals sign is ignored. Variables assigned in this way are visible only to less. If a variable is specified in the system environment and also in a lesskey file, the value in the lesskey file takes precedence. Although the lesskey file can be used to override variables set in the environment, the main purpose of assigning variables in the lesskey file is simply to have all less configuration information stored in one file.

#env
LESS = -i
LESSCHARSET = latin1