Lynx Line Editor Bash-Like Key Binding

Lynx invokes a built-in Line Editor for entering strings in response to prompts, in forms, and for email messages if an external editor has not been defined. Alternative key bindings are normally available (unless Lynx was configured with --disable-alt-bindings). If available, they may be selected via the “o”ptions menu, or by editing lineedit_mode in the “.lynxrc” file.

You can always see the current set of key-bindings in Lynx by opening the special URL LYNXEDITMAP:. This page is provided for those not using Lynx.

Note: setting emacs/vi keys ON has no direct effect on line-editor bindings.

"next" means the character "under" a box or underline style cursor; it means "to the immediate right of" an I-beam (between characters) type cursor.

For entering strings in response to prompts (that is, when not editing form text fields), some keys have different actions: TAB tries to complete input based on previous response; Up-Arrow and Down-Arrow may offer previous response and next response, respectively, from recall buffer for some prompts.

Ctrl-w can only be used for editing functions if its default KEYMAP to REFRESH is changed. This can be done in the lynx.cfg file, for example with the line "KEYMAP:^W:DO_NOTHING". This also applies for other keys: as long as the key's action is mapped to REFRESH, either with an explicit KEYMAP in lynx.cfg or by default, the key's Line Editor binding is disabled.

These keys invoke special behavior when pressed twice in a row: Ctrl-e Ctrl-e calls the external editor for changing the text in a textarea (if available). Ctrl-k Ctrl-k will move to the next link, so that all lines in a textarea can be conveniently cleared by repeating Ctrl-k.

Key is likely unavailable for Lynx, because it is interpreted by operating system, comm program, or curses library, or swallowed as part of escape sequence recognition. Binding is provided for the benefit of those where this does not apply.

where [FORM] is marked, indicates that the binding is effective only in form text fields. It is ignored by Line Editor elsewhere.

When a text input field, including a textarea line, is selected, the Line Editor functions get a first grab at the keys entered. If a key has no function defined in the Line Editor binding, it can either be ignored, or passed on for normal key command handling, where modifiers like Ctrl-x or Meta currently have no effect (see the Key Map Page accessible with the key K for current information).