/** * less's lesskey action NAMES against the numeric codes a compiled file * carries - `lesskey_parse.c`'s cmdnames/editnames tables resolved * through `cmd.h`. * * The pager itself never needs this: reading a binding only has to * reach an action, which `ACTION_CODES` already does. WRITING one * does, because the byte in the file is less's code and nothing else, * and so does rendering a binary back as source. Both directions live * here so they cannot drift apart. * * GENERATED from the vendored less/ source (707x) by * `tools/gen-lesskey-codes.py`. Regenerate rather than edit. */ /** A_EXTRA: OR'd into the action byte when an extra string follows. */ export declare const A_EXTRA = 128; /** EV_OK: the #env section's action byte, always with A_EXTRA. */ export declare const EV_OK = 1; /** #command action names, like less's cmdnames[]. */ export declare const COMMAND_CODES: Record; /** #line-edit action names, like less's editnames[]. */ export declare const EDIT_ACTION_CODES: Record; /** * A code back to ONE name, for rendering a binary as source. * * less lets several names share a code - "end" and "goto-end" are both * A_GOEND - so this keeps the first less lists, which is also the first * alphabetically. Any of them compiles back to the same byte. */ export declare const COMMAND_NAMES: Record; /** The same, for the #line-edit section. */ export declare const EDIT_ACTION_NAMES: Record; /** * SK_SPECIAL_KEY, the byte that opens a special-key blob in a compiled * file: CONTROL('K'). A literal ^K in a key sequence is stored as the * SK_CONTROL_K blob instead, so that this byte always means "blob". */ export declare const SK_SPECIAL_KEY = 11; /** SK_CONTROL_K: how a literal ^K is stored. */ export declare const SK_CONTROL_K = 40; /** * Every \k form and the SK_* code it compiles to, out of less's tstr. * * A compiled file stores the blob `SK_SPECIAL_KEY 6 1 1 1`, not * a terminal sequence - the reader expands it through terminfo when it * loads. Which is why this is a different table from the pager's own * \k handling, and a superset of it: the keypad forms have no * capability to resolve to, but they still compile. */ export declare const SPECIAL_KEY_CODES: Record; /** * less's built-in bindings, written out as lesskey source. * * --edit-lesskey opens this when a session has no lesskey of any kind, * so the editor holds what the keys ALREADY do rather than an empty * file - every binding is there to be changed or deleted, and the * shape of the syntax comes with it. * * It is less's own cmdtable/edittable (decode.c), not a description of * them: compile it and you get the defaults back. The two paste * markers appear commented out, because A_START_PASTE and A_END_PASTE * have no lesskey name to write. */ export declare const DEFAULT_KEYMAP: string[];