Modes and Submodules

The Elvish editor has different modes, and exactly one mode is active at the same time. Each mode has its own UI and keybindings. For instance, the default insert mode lets you modify the current command. The completion mode (triggered by Tab by default) shows you all candidates for completion, and you can use arrow keys to navigate those candidates.

@ttyshot completion-mode

Each mode has its own submodule under edit:. For instance, builtin functions and configuration variables for the completion mode can be found in the edit:completion: module.

The primary modes supported now are insert, completion, navigation, history, histlist, location, and lastcmd. The last 4 are “listing modes”, and their particularity is documented below.

Prompts

Elvish has two prompts: the (normal) left-hand prompt and the right-side prompt (rprompt). Most of this section only documents the left-hand prompt, but API for rprompt is the same other than the variable name: just replace prompt with rprompt.

To customize the prompt, assign a function to edit:prompt. The function may write value outputs or byte outputs:

•

Value outputs may be either strings or styled values; they are joiend with no spaces in between.

•

Byte outputs are output as-is, including any newlines. Any SGR escape sequences (https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_parameters) included in the byte outputs will be parsed, but any other escape sequences or control character will be removed.

If you mix value and byte outputs, the order in which they appear is non-deterministic.

Prefer using styled to output styled text; the support for SGR escape sequences is mostly for compatibility with external cross-shell prompts.

The default prompt and rprompt are equivalent to:

edit:prompt = { tilde-abbr $pwd; put '> ' }
edit:rprompt = (constantly (styled (whoami)@(hostname) inverse))
    

More prompt functions:

~> edit:prompt = { tilde-abbr $pwd; styled '> ' green }
~> # ">" is now green
~> edit:prompt = { echo '$' }
$
# Cursor will be on the next line as `echo` outputs a trailing newline
    

Stale Prompt

Elvish never waits for the prompt function to finish. Instead, the prompt function is always executed on a separate thread, and Elvish updates the screen when the function finishes.

However, this can be misleading when the function is slow: this means that the prompt on the screen may not contain the latest information. To deal with this, if the prompt function does not finish within a certain threshold - by default 0.2 seconds, Elvish marks the prompt as stale: it still shows the old stale prompt content, but transforms it using a stale transformer. The default stale transformer applies reverse-video to the whole prompt.

The threshold is customizable with $edit:prompt-stale-threshold; it specifies the threshold in seconds.

The transformer is customizable with $edit:prompt-stale-transform. It is a function; the function is called with one argument, a styled text, and the output is interpreted in the same way as prompt functions. Some examples are:

# The following effectively disables marking of stale prompt.
edit:prompt-stale-transform = [x]{ put $x }
# Show stale prompts in inverse; equivalent to the default.
edit:prompt-stale-transform = [x]{ styled $x inverse }
# Gray out stale prompts.
edit:prompt-stale-transform = [x]{ styled $x bright-black }
    

To see the transformer in action, try the following example (assuming default $edit:prompt-stale-transform):

n = 0
edit:prompt = { sleep 2; put $n; n = (+ $n 1); put ': ' }
edit:-prompt-eagerness = 10 # update prompt on each keystroke
edit:prompt-stale-threshold = 0.5
    

And then start typing. Type one character; the prompt becomes inverse after 0.5 second: this is when Elvish starts to consider the prompt as stale. The prompt will return normal after 2 seconds, and the counter in the prompt is updated: this is when the prompt function finishes.

Another thing you will notice is that, if you type a few characters quickly (in less than 2 seconds, to be precise), the prompt is only updated twice. This is because Elvish never does two prompt updates in parallel: prompt updates are serialized. If a prompt update is required when the prompt function is still running, Elvish simply queues another update. If an update is already queued, Elvish does not queue another update. The reason why exactly two updates happen in this case, and how this algorithm ensures freshness of the prompt is left as an exercise to the reader.

Prompt Eagerness

The occasions when the prompt should get updated can be controlled with $edit:-prompt-eagerness:

•

The prompt is always updated when the editor becomes active – when Elvish starts, or a command finishes execution, or when the user presses Enter.

•

If $edit-prompt-eagerness >= 5, it is updated when the working directory changes.

•

If $edit-prompt-eagerness >= 10, it is updated on each keystroke.

The default value is 5.

RPrompt Persistency

By default, the rprompt is only shown while the editor is active: as soon as you press Enter, it is erased. If you want to keep it, simply set $edit:rprompt-persistent to $true:

edit:rprompt-persistent = $true
    

Keybindings

Each mode has its own keybinding, accessible as the binding variable in its module. For instance, the binding table for insert mode is $edit:insert:binding. To see current bindings, simply print the binding table: pprint $edit:insert:binding (replace insert with any other mode).

A binding tables is simply a map that maps keys to functions. For instance, to bind Alt-x in insert mode to exit Elvish, simply do:

edit:insert:binding[Alt-x] = { exit }
    

Outputs from a bound function always appear above the Elvish prompt. You can see this by doing the following:

edit:insert:binding[Alt-x] = { echo 'output from a bound function!' }
    

and press Alt-x in insert mode. It allows you to put debugging outputs in bound functions without messing up the terminal.

Internally, this is implemented by connecting their output to a pipe. This does the correct thing in most cases, but if you are sure you want to do something to the terminal, redirect the output to /dev/tty. For instance, the following binds Ctrl-L to clearing the terminal:

edit:insert:binding[Ctrl-L] = { clear > /dev/tty }
    

Bound functions have their inputs redirected to /dev/null.

Format of Keys

Key modifiers and names are case sensitive. This includes single character key names such as x and Y as well as function key names such as Enter.

Key names have zero or more modifiers from the following symbols:

    A  Alt


    C  Ctrl


    M  Meta


    S  Shift
    

Modifiers, if present, end with either a - or +; e.g., S-F1, Ctrl-X or Alt+Enter. You can stack modifiers; e.g., C+A-X.

The key name may be a simple character such as x or a function key from these symbols:

    F1  F2  F3  F4  F5  F6  F7  F8  F9  F10  F11  F12


    Up  Down  Right  Left


    Home  Insert  Delete  End  PageUp  PageDown


    Tab  Enter  Backspace
    

Note: Tab is an alias for "\t" (aka Ctrl-I), Enter for "\n" (aka Ctrl-J), and Backspace for "\x7F" (aka Ctrl-?).

Note: The Shift modifier is only applicable to function keys such as F1. You cannot write Shift-m as a synonym for M.

TODO: Document the behavior of the Shift modifier.

Listing Modes

The modes histlist, loc and lastcmd are all listing modes: They all show a list, and you can filter items and accept items.

Because they are very similar, you may want to change their bindings at the same time. This is made possible by the $edit:listing:binding binding table (listing is not a “real” mode but an “abstract” mode). These modes still have their own binding tables like $edit:histlist:binding, and bindings there have higher precedence over those in the shared $edit:listing:binding table.

Moreover, there are a lot of builtin functions in the edit:listing module like edit:listing:down (for moving down selection). They always apply to whichever listing mode is active.

Caveat: Bindings to Start Modes

Note that keybindings to start modes live in the binding table of the insert mode, not the target mode. For instance, if you want to be able to use Alt-l to start location mode, you should modify $edit:insert:binding[Alt-l]:

edit:insert:binding[Alt-l] = { edit:location:start }
    

One tricky case is the history mode. You can press ▲︎ to start searching for history, and continue pressing it to search further. However, when the first press happens, the editor is in insert mode, while with subsequent presses, the editor is in history mode. Hence this binding actually relies on two entries, $edit:insert:binding[Up] and $edit:history:binding[Up].

So for instance if you want to be able to use Ctrl-P for this, you need to modify both bindings:

edit:insert:binding[Ctrl-P] =  { edit:history:start }
edit:history:binding[Ctrl-P] = { edit:history:up }
    

Completion API

Argument Completer

There are two types of completions in Elvish: completion for internal data and completion for command arguments. The former includes completion for variable names (e.g. echo $Tab) and indices (e.g. echo $edit:insert:binding[Tab). These are the completions that Elvish can provide itself because they only depend on the internal state of Elvish.

The latter, in turn, is what happens when you type e.g. catTab. Elvish cannot provide completions for them without full knowledge of the command.

Command argument completions are programmable via the $edit:completion:arg-completer variable. When Elvish is completing an argument of command $x, it will call the value stored in $edit:completion:arg-completer[$x], with all the existing arguments, plus the command name in the front.

For example, if the user types man 1Tab, Elvish will call:

$edit:completion:arg-completer[man] man 1
    

If the user is starting a new argument when hitting Tab, Elvish will call the completer with a trailing empty string. For instance, if you do man 1SpaceTab, Elvish will call:

$edit:completion:arg-completer[man] man 1 ""
    

The output of this call becomes candidates. There are several ways of outputting candidates:

•

Writing byte output, e.g. “echo cand1; echo cand2”. Each line becomes a candidate. This has the drawback that you cannot put newlines in candidates. Only use this if you are sure that you candidates will not contain newlines – e.g. package names, usernames, but not file names, etc..

•

Write strings to value output, e.g. “put cand1 cand2”. Each string output becomes a candidate.

•

Use the edit:complex-candidate command:

After receiving your candidates, Elvish will match your candidates against what the user has typed. Hence, normally you don’t need to (and shouldn’t) do any matching yourself.

That means that in many cases you can (and should) simply ignore the last argument to your completer. However, they can be useful for deciding what kind of things to complete. For instance, if you are to write a completer for ls, you want to see whether the last argument starts with - or not: if it does, complete an option; and if not, complete a filename.

Here is a very basic example of configuring a completer for the apt command. It only supports completing the install and remove command and package names after that:

all-packages = [(apt-cache search '' | eawk [0 1 @rest]{ put $1 })]
edit:completion:arg-completer[apt] = [@args]{


    n = (count $args)


    if (== $n 2) {


        # apt x<Tab> -- complete a subcommand name


        put install uninstall


    } elif (== $n 3) {


        put $@all-packages


    }
}
    

Here is another slightly more complex example for the git command. It supports completing some common subcommands and then branch names after that:

fn all-git-branches {


    # Note: this assumes a recent version of git that supports the format


    # string used.


    git branch -a --format="%(refname:strip=2)" | eawk [0 1 @rest]{ put $1 }
}
common-git-commands = [


  add branch checkout clone commit diff init log merge


  pull push rebase reset revert show stash status
]
edit:arg-completer[git] = [@args]{


    n = (count $args)


    if (== $n 2) {


        put $@common-git-commands


    } elif (>= $n 3) {


        all-git-branches


    }
}
    

Matcher

As stated above, after the completer outputs candidates, Elvish matches them with them with what the user has typed. For clarity, the part of the user input that is relevant to tab completion is called for the seed of the completion. For instance, in echo xTab, the seed is x.

Elvish first indexes the matcher table – $edit:completion:matcher – with the completion type to find a matcher. The completion type is currently one of variable, index, command, redir or argument. If the $edit:completion:matcher lacks the suitable key, $edit:completion:matcher[''] is used.

Elvish then calls the matcher with one argument – the seed, and feeds the text of all candidates to the input. The mather must output an identical number of booleans, indicating whether the candidate should be kept.

As an example, the following code configures a prefix matcher for all completion types:

edit:completion:matcher[''] = [seed]{ each [cand]{ has-prefix $cand $seed } }
    

Elvish provides three builtin matchers, edit:match-prefix, edit:match-substr and edit:match-subseq. In addition to conforming to the matcher protocol, they accept two options &ignore-case and &smart-case. For example, if you want completion of arguments to use prefix matching and ignore case, use:

edit:completion:matcher[argument] = [seed]{ edit:match-prefix $seed &ignore-case=$true }
    

The default value of $edit:completion:matcher is [&''=$edit:match-prefix~], hence that candidates for all completion types are matched by prefix.

Hooks

Hooks are functions that are executed at certain points in time. In Elvish, this functionality is provided by lists of functions.

There are current two hooks:

•

$edit:before-readline, whose elements are called before the editor reads code, with no arguments.

•

$edit:after-readline, whose elements are called, after the editor reads code, with a sole element – the line just read.

Example usage:

edit:before-readline = [{ echo 'going to read' }]
edit:after-readline = [[line]{ echo 'just read '$line }]
    

Then every time you accept a chunk of code (and thus leaving the editor), just read followed by the code is printed; and at the very beginning of an Elvish session, or after a chunk of code is executed, going to read is printed.

Word types

The editor supports operating on entire “words”. As intuitive as the concept of “word” is, there is actually no single definition for the concept. The editor supports the following three definitions of words:

•

A big word, or simply word, is a sequence of non-whitespace characters. This definition corresponds to the concept of “WORD” in vi.

•

A small word is a sequence of alphanumerical characters (“alnum small word”), or a sequence of non-alphanumerical, non-whitespace characters (“punctuation small word”). This definition corresponds to the concept of “word” in vi and zsh.

•

An alphanumerical word is a sequence of alphanumerical characters. This definition corresponds to the concept of “word” in bash.

Whitespace characters are those with the Unicode Whitespace (https://en.wikipedia.org/wiki/Whitespace_character#Unicode) property. Alphanumerical characters are those in the Unicode Letter or Number category.

A word boundary is an imaginary zero-length boundary around a word.

To see the difference between these definitions, consider the following string: abc++ /* xyz:

•

It contains three (big) words: abc++, /* and xyz.

•

It contains four small words, abc, ++, /* and xyz. Among them, abc and xyz are alnum small words, while ++ and /* are punctuation small words.

•

It contains two alnum words, abc and xyz.

$edit:abbr

A map from (simple) abbreviations to their expansions.

An abbreviation is replaced by its expansion when it is typed in full and consecutively, without being interrupted by the use of other editing functionalities, such as cursor movements.

If more than one abbreviations would match, the longest one is used.

Examples:

edit:abbr['||'] = '| less'
edit:abbr['>dn'] = '2>/dev/null'
    

With the definitions above, typing || anywhere expands to | less, and typing >dn anywhere expands to 2>/dev/null. However, typing a |, moving the cursor left, and typing another | does not expand to | less, since the abbreviation || was not typed consecutively.

@cf edit:small-word-abbr

$edit:add-cmd-filters

List of filters to run before adding a command to history.

A filter is a function that takes a command as argument and outputs a boolean value. If any of the filters outputs $false, the command is not saved to history, and the rest of the filters are not run. The default value of this list contains a filter which ignores command starts with space.

$edit:after-readline

A list of functions to call after each readline cycle. Each function is called with a single string argument containing the code that has been read.

$edit:before-readline

A list of functions to call before each readline cycle. Each function is called without any arguments.

$edit:completion:arg-completer

A map containing argument completers.

$edit:completion:binding

Keybinding for the completion mode.

$edit:completion:matcher

A map mapping from context names to matcher functions. See the Matcher section.

$edit:current-command

Contains the content of the current input. Setting the variable will cause the cursor to move to the very end, as if edit-dot = (count $edit:current-command) has been invoked.

This API is subject to change.

$edit:-dot

Contains the current position of the cursor, as a byte position within $edit:current-command.

$edit:exceptions

A list of exceptions thrown from callbacks such as prompts. Useful for examining tracebacks and other metadata.

$edit:-instant:binding

Binding for the instant mode.

$edit:location:hidden

A list of directories to hide in the location addon.

$edit:location:pinned

A list of directories to always show at the top of the list of the location addon.

$edit:location:workspaces

A map mapping types of workspaces to their patterns.

$edit:max-height

Maximum height the editor is allowed to use, defaults to +Inf.

By default, the height of the editor is only restricted by the terminal height. Some modes like location mode can use a lot of lines; as a result, it can often occupy the entire terminal, and push up your scrollback buffer. Change this variable to a finite number to restrict the height of the editor.

$edit:navigation:binding

Keybinding for the navigation mode.

$edit:navigation:width-ratio

A list of 3 integers, used for specifying the width ratio of the 3 columns in navigation mode.

$edit:prompt

See Prompts.

$edit:-prompt-eagerness

See Prompt Eagerness.

$edit:prompt-stale-threshold

See Stale Prompt.

$edit:prompt-stale-transformer.

See Stale Prompt.

$edit:rprompt

See Prompts.

$edit:-rprompt-eagerness

See Prompt Eagerness.

$edit:rprompt-persistent

See RPrompt Persistency.

$edit:rprompt-stale-threshold

See Stale Prompt.

$edit:rprompt-stale-transformer.

See Stale Prompt.

$edit:selected-file

Name of the currently selected file in navigation mode. $nil if not in navigation mode.

$edit:small-word-abbr

A map from small-word abbreviations and their expansions.

A small-word abbreviation is replaced by its expansion after it is typed in full and consecutively, and followed by another character (the trigger character). Furthermore, the expansion requires the following conditions to be satisfied:

•

The end of the abbreviation must be adjacent to a small-word boundary, i.e. the last character of the abbreviation and the trigger character must be from two different small-word categories.

•

The start of the abbreviation must also be adjacent to a small-word boundary, unless it appears at the beginning of the code buffer.

•

The cursor must be at the end of the buffer.

If more than one abbreviations would match, the longest one is used.

As an example, with the following configuration:

edit:small-word-abbr['gcm'] = 'git checkout master'
    

In the following scenarios, the gcm abbreviation is expanded:

•

With an empty buffer, typing gcm and a space or semicolon;

•

When the buffer ends with a space, typing gcm and a space or semicolon.

The space or semicolon after gcm is preserved in both cases.

In the following scenarios, the gcm abbreviation is not expanded:

•

With an empty buffer, typing Xgcm and a space or semicolon (start of abbreviation is not adjacent to a small-word boundary);

•

When the buffer ends with X, typing gcm and a space or semicolon (end of abbreviation is not adjacent to a small-word boundary);

•

When the buffer is non-empty, move the cursor to the beginning, and typing gcm and a space (cursor not at the end of the buffer).

This example shows the case where the abbreviation consists of a single small word of alphanumerical characters, but that doesn’t have to be the case. For example, with the following configuration:

edit:small-word-abbr['>dn'] = ' 2>/dev/null'
    

The abbreviation >dn starts with a punctuation character, and ends with an alphanumerical character. This means that it is expanded when it borders a whitespace or alphanumerical character to the left, and a whitespace or punctuation to the right; for example, typing ls>dn; will expand it.

Some extra examples of small-word abbreviations:

edit:small-word-abbr['gcp'] = 'git cherry-pick -x'
edit:small-word-abbr['ll'] = 'ls -ltr'
    

If both a simple abbreviation and a small-word abbreviation can be expanded, the simple abbreviation has priority.

@cf edit:abbr

edit:add-var

edit:add-var $name $value
    

Declares a new variable in the REPL. The new variable becomes available during the next REPL cycle.

Equivalent to running var $name = $value at the REPL, but $name can be dynamic.

Example:

~> edit:add-var foo bar
~> put $foo
▶ bar
    

edit:add-vars

edit:add-vars $map
    

Takes a map from strings to arbitrary values. Equivalent to calling edit:add-var for each key-value pair in the map.

edit:binding-table

Converts a normal map into a binding map.

edit:close-listing

Closes any active listing.

edit:command-history

Outputs the entire command history as a stream of maps. Each map has a id key that identifies the sequence number of the entry, and a cmd key that identifies the content.

Use indexing to extract individual entries. For example, to extract the content of the last command, do this:

edit:command-history | put [(all)][-1][cmd]
    

edit:complete-filename

edit:complete-filename $args...
    

Produces a list of filenames found in the directory of the last argument. All other arguments are ignored. If the last argument does not contain a path (either absolute or relative to the current directory), then the current directory is used. Relevant files are output as edit:complex-candidate objects.

This function is the default handler for any commands without explicit handlers in $edit:completion:arg-completer. See Argument Completer.

Example:

~> edit:complete-filename ''
▶ (edit:complex-candidate Applications &code-suffix=/ &style='01;34')
▶ (edit:complex-candidate Books &code-suffix=/ &style='01;34')
▶ (edit:complex-candidate Desktop &code-suffix=/ &style='01;34')
▶ (edit:complex-candidate Docsafe &code-suffix=/ &style='01;34')
▶ (edit:complex-candidate Documents &code-suffix=/ &style='01;34')
...
~> edit:complete-filename .elvish/
▶ (edit:complex-candidate .elvish/aliases &code-suffix=/ &style='01;34')
▶ (edit:complex-candidate .elvish/db &code-suffix=' ' &style='')
▶ (edit:complex-candidate .elvish/epm-installed &code-suffix=' ' &style='')
▶ (edit:complex-candidate .elvish/lib &code-suffix=/ &style='01;34')
▶ (edit:complex-candidate .elvish/rc.elv &code-suffix=' ' &style='')
    

edit:complete-getopt

edit:complete-getopt $args $opt-specs $arg-handlers
    

Produces completions according to a specification of accepted command-line options (both short and long options are handled), positional handler functions for each command position, and the current arguments in the command line. The arguments are as follows:

•

$args is an array containing the current arguments in the command line (without the command itself). These are the arguments as passed to the Argument Completer function.

•

$opt-specs is an array of maps, each one containing the definition of one possible command-line option. Matching options will be provided as completions when the last element of $args starts with a dash, but not otherwise. Each map can contain the following keys (at least one of short or long needs to be specified):

•

$arg-handlers is an array of functions, each one returning the possible completions for that position in the arguments. Each function receives as argument the last element of $args, and should return zero or more possible values for the completions at that point. The returned values can be plain strings or the output of edit:complex-candidate. If the last element of the list is the string ..., then the last handler is reused for all following arguments.

Example:

~> fn complete [@args]{


     opt-specs = [ [&short=a &long=all &desc="Show all"]


                   [&short=n &desc="Set name" &arg-required=$true


                    &completer= [_]{ put name1 name2 }] ]


     arg-handlers = [ [_]{ put first1 first2 }


                      [_]{ put second1 second2 } ... ]


     edit:complete-getopt $args $opt-specs $arg-handlers


   }
~> complete ''
▶ first1
▶ first2
~> complete '-'
▶ (edit:complex-candidate -a &display='-a (Show all)')
▶ (edit:complex-candidate --all &display='--all (Show all)')
▶ (edit:complex-candidate -n &display='-n (Set name)')
~> complete -n ''
▶ name1
▶ name2
~> complete -a ''
▶ first1
▶ first2
~> complete arg1 ''
▶ second1
▶ second2
~> complete arg1 arg2 ''
▶ second1
▶ second2
    

edit:completion:close

Closes the completion mode UI.

edit:completion:smart-start

Starts the completion mode. However, if all the candidates share a non-empty prefix and that prefix starts with the seed, inserts the prefix instead.

edit:completion:start

Start the completion mode.

edit:complex-candidate

edit:complex-candidate $stem &display='' &code-suffix=''
    

Builds a complex candidate. This is mainly useful in argument completers.

The &display option controls how the candidate is shown in the UI. It can be a string or a styled text. If it is empty, $stem is used.

The &code-suffix option affects how the candidate is inserted into the code when it is accepted. By default, a quoted version of $stem is inserted. If $code-suffix is non-empty, it is added to that text, and the suffix is not quoted.

edit:-dump-buf

Dumps the current UI buffer as HTML. This command is used to generate “ttyshots” on the website (https://elv.sh).

Example:

ttyshot = ~/a.html
edit:insert:binding[Ctrl-X] = { edit:-dump-buf > $tty }
    

edit:end-of-history

Adds a notification saying “End of history”.

edit:history:fast-forward

Import command history entries that happened after the current session started.

edit:insert-at-dot

edit:insert-at-dot $text
    

Inserts the given text at the dot, moving the dot after the newly inserted text.

edit:insert-last-word

Inserts the last word of the last command.

edit:insert-raw

Requests the next terminal input to be inserted uninterpreted.

edit:-instant:start

Starts the instant mode. In instant mode, any text entered at the command line is evaluated immediately, with the output displayed.

WARNING: Beware of unintended consequences when using destructive commands. For example, if you type sudo rm -rf /tmp/* in the instant mode, Elvish will attempt to evaluate sudo rm -rf / when you typed that far.

edit:key

edit:key $string
    

Parses a string into a key.

edit:kill-alnum-word-left

Deletes the the last alnum word to the left of the dot.

edit:kill-alnum-word-right

Deletes the the first alnum word to the right of the dot.

edit:kill-line-left

Deletes the text between the dot and the start of the current line.

edit:kill-line-right

Deletes the text between the dot and the end of the current line.

edit:kill-rune-left

Kills one rune right of the dot. Does nothing if the dot is at the end of the buffer.

edit:kill-small-word-left

Deletes the the last small word to the left of the dot.

edit:kill-small-word-right

Deletes the the first small word to the right of the dot.

edit:kill-word-left

Deletes the the last word to the left of the dot.

edit:kill-word-right

Deletes the the first word to the right of the dot.

edit:listing:accept

Accepts the current selected listing item.

edit:listing:accept-close

Accepts the current selected listing item and closes the listing.

edit:listing:down

Moves the cursor down in listing mode.

edit:listing:down-cycle

Moves the cursor down in listing mode, or to the first item if the last item is currently selected.

edit:listing:left

Moves the cursor left in listing mode.

edit:listing:page-down

Moves the cursor down one page.

edit:listing:page-up

Moves the cursor up one page.

edit:listing:right

Moves the cursor right in listing mode.

edit:listing:start-custom

Starts a custom listing addon.

edit:listing:up

Moves the cursor up in listing mode.

edit:listing:up-cycle

Moves the cursor up in listing mode, or to the last item if the first item is currently selected.

edit:match-prefix

edit:match-prefix $seed $inputs?
    

For each input, outputs whether the input has $seed as a prefix. Uses the result of to-string for non-string inputs.

Roughly equivalent to the following Elvish function, but more efficient:

use str
fn match-prefix [seed @input]{


  each [x]{ str:has-prefix (to-string $x) $seed } $@input
}
    

edit:match-subseq

edit:match-subseq $seed $inputs?
    

For each input, outputs whether the input has $seed as a subsequence (https://en.wikipedia.org/wiki/Subsequence). Uses the result of to-string for non-string inputs.

edit:match-substr

edit:match-substr $seed $inputs?
    

For each input, outputs whether the input has $seed as a substring. Uses the result of to-string for non-string inputs.

Roughly equivalent to the following Elvish function, but more efficient:

use str
fn match-substr [seed @input]{


  each [x]{ str:has-contains (to-string $x) $seed } $@input
}
    

edit:move-dot-down

Moves the dot down one line, trying to preserve the visual horizontal position. Does nothing if dot is already on the last line of the buffer.

edit:move-dot-eol

Moves the dot to the end of the current line.

edit:move-dot-left

Moves the dot left one rune. Does nothing if the dot is at the beginning of the buffer.

edit:move-dot-left-alnum-word

Moves the dot to the beginning of the last alnum word to the left of the dot.

edit:move-dot-left-small-word

Moves the dot to the beginning of the last small word to the left of the dot.

edit:move-dot-left-word

Moves the dot to the beginning of the last word to the left of the dot.

edit:move-dot-right

Moves the dot right one rune. Does nothing if the dot is at the end of the buffer.

edit:move-dot-right-alnum-word

Moves the dot to the beginning of the first alnum word to the right of the dot.

edit:move-dot-right-small-word

Moves the dot to the beginning of the first small word to the right of the dot.

edit:move-dot-right-word

Moves the dot to the beginning of the first word to the right of the dot.

edit:move-dot-sol

Moves the dot to the start of the current line.

edit:move-dot-up

Moves the dot up one line, trying to preserve the visual horizontal position. Does nothing if dot is already on the first line of the buffer.

edit:navigation:insert-selected

Inserts the selected filename.

edit:navigation:insert-selected-and-quit

Inserts the selected filename and closes the navigation addon.

edit:navigation:start

Start the navigation mode.

edit:navigation:trigger-filter

Toggles the filtering status of the navigation addon.

edit:navigation:trigger-shown-hidden

Toggles whether the navigation addon should be showing hidden files.

edit:redraw

edit:redraw &full=$false
    

Triggers a redraw.

The &full option controls whether to do a full redraw. By default, all redraws performed by the line editor are incremental redraws, updating only the part of the screen that has changed from the last redraw. A full redraw updates the entire command line.

edit:replace-input

edit:replace-input $text
    

Equivalent to assigning $text to $edit:current-command.

edit:return-eof

Causes the Elvish REPL to terminate. Internally, this works by raising a special exception.

edit:return-line

Causes the Elvish REPL to end the current read iteration and evaluate the code it just read.

edit:smart-enter

Inserts a literal newline if the current code is not syntactically complete Elvish code. Accepts the current line otherwise.

edit:wordify

edit:wordify $code
    

Breaks Elvish code into words.