zsh-5.8.1/Doc/zsh.info-3

374      whitespace included use the following key binding:
663 expand-cmd-path
666 expand-or-complete (TAB) (unbound) (TAB)
670 expand-or-complete-prefix
673 expand-history (ESC-space ESC-!) (unbound) (unbound)
676 expand-word (^X*) (unbound) (unbound)
682 list-expand (^Xg ^XG) (^G) (^G)
693 menu-expand-or-complete
694      Like expand-or-complete, except that menu completion is used.
815      expand-or-complete and expand-or-complete-prefix.
1112 context for highlighting, then a colon, then a comma-separated list of
1113 the types of highlighting to apply in that context.
1143      This context is used in completion for characters that are marked
1198      No highlighting is applied to the given context.  It is not useful
1239      The characters in the given context are shown in a bold font.  Not
1243      The characters in the given context are shown in the terminal's
1252      The characters in the given context are shown underlined.  Some
1302 context, the defaults applied are equivalent to
1340      zle -C complete expand-or-complete completer
1344 expand-or-complete, expand-or-complete-prefix, menu-complete,
1345 menu-expand-or-complete, reverse-menu-complete, list-choices, or
1358 widget, in this case expand-or-complete.
1460     context
1461           This will be set by the completion code to the overall context
1472                expansion beginning with ${.  This context will also be
2515 The context that decides what completion is to be performed may be
2520    * a special context, denoting an element in the shell's syntax.  For
2524 A full context specification contains other elements, as we shall
2535 these are tags.  They also appear as the rightmost element in a context
2547 current context, and uses that to modify its behavior.  The full
2548 description of context handling, which determines how tags and other
2549 elements of the context influence the behaviour of styles, is described
2642 default, and the TAB key is bound to expand-or-complete, compinit will
2648 name, e.g. `.expand-or-complete'.
2741      (or special context) SERVICE was being completed instead.  This
2750      called when completion is attempted for a command or context that
2764      complete-word, delete-char-or-list, expand-or-complete,
2765      expand-or-complete-prefix, list-choices, menu-complete,
2766      menu-expand-or-complete, or reverse-menu-complete.  If the
2839      `-default-' context will not be called, but functions defined for
2863 most cases the context -CONTEXT- is implemented by a corresponding
2864 function _CONTEXT, for example the context `-tilde-' and the function
2867 The contexts -redirect- and -value- allow extra context-specific
2869 context calling the function _dispatch.)  The extra information is
2872 For the -redirect- context, the extra information is in the form
2877 For the -value- context, the form is `-value-,NAME,COMMAND', where NAME
2890 function to handle the context.
2953      command or context from being overwritten.
2964      pattern context.  If it is set to a value containing the substring
2970      calling the pattern-context one, which can mangle the display of
2979      expand-or-complete, expand-or-complete-prefix, list-choices,
2980      menu-complete, menu-expand-or-complete, and reverse-menu-complete,
3026 completion system begins building the context.  The context represents
3033 The context starts out very generic ("we are beginning a completion")
3036 variable name" and so on).  Therefore the context will vary during the
3039 This context information is condensed into a string consisting of
3041 context' in the remainder of the documentation.  Note that a user of
3042 the completion system rarely needs to compose a context string, unless
3045 which is matched against a context when needed to look up
3046 context-sensitive options that configure the completion system.
3048 The next few paragraphs explain how a context is composed within the
3055 The context string always consists of a fixed set of fields, separated
3064      the completion system.  This distinguishes the context from those
3099      a certain context.  Any completion function may use any tag name
3103 The context is gradually put together as the functions are executed,
3108 known.  For example, the context name
3131 When looking up styles the completion system uses full context names,
3133 of two things: the context, which is matched to the most specific (best
3147 value yes in every context inside the completion system, unless that
3148 context has a more specific definition.  It is best to avoid giving the
3149 context as `*' in case the style has some meaning outside the
3267      when only the FUNCTION field of the context name is set
3417      used to look up the values of the expand, ambiguous and
3518 FUNCTION field of the context will be set so that a style using the
3527      for the current context.  If it is set to `true' and any of the
3704      COMPLETER field of the context will contain the name of the
3707      is the name of the completer to call, but the context will contain
3708      the user-defined NAME in the COMPLETER field of the context.  If
3709      the NAME starts with a hyphen, the string for the context will be
3718      field of the context.  Normally, using the same completer more
3720      form, because otherwise the context name will be the same in all
3743      command will try to expand disabled aliases, too.  The default is
3758 expand
3773      This style may be set for any completion context.  It specifies
3774      additional strings that will always be completed in that context.
3780      It is important to use a sufficiently restrictive context when
3834      the particular context.  Names for which no type is specified will
3950      given context to be split at the point where any of the characters
4020      completer and bindable command will try to expand global aliases.
4070      If this is set to `true', matches for the given context will not
4106      `other' for a general context such as `:completion:*'.  This is
4213      the context will already have been set to one of correct-NUM or
4265      The context always starts with `:completion:history-words'.
4310      This is tested for each tag valid in the current context as well
4392      context.  Its value is placed before any match specifications
4422      completers by using the third field of the context.  This applies
4448      If the style is unset in any context no match specification is
4512      If this is `true' in the context of any of the tags defined for
4647      field in the context name set to correct-NUM or approximate-NUM,
4653      a given context.  For example,
4856      set for the context, the standard behaviour of the calling widget
4859      The style is tested first against the full context including the
4860      tag, and if that fails to produce a value against the context
4920      first try to expand all substitutions in the string (such as
4935      particular context will be used.
4966           all other possible tags for the context had been listed.
5075      If no tag-order style has been defined for a context, the strings
5117      If this is set, the completion caching layer is activated for any
5146      can be completed as well.  This style is not use in any context
5224 context and the other arguments give a command name and arguments to
5230 context `:completion::complete:...'.
5287      shown, and so on.  It modifies the completer name in the context
5351      context-sensitive manner, i.e. using the settings defined with the
5361      Before trying to find a function for a specific context, _complete
5377      value is taken as the name of the context to use and the function
5378      defined for that context will be called.  For this purpose, there
5379      is a special context named -command-line- that completes whole
5389      completer field in the context name is correct.
5421      needs to be invoked with complete-word, not expand-or-complete
5422      (the default binding for TAB), as otherwise the string will be
5459      completers such as _expand to expand the pattern. The standard
5540      effect is similar to the expand-or-complete-prefix command.
5544      completers set for the current context is used -- except, of
5561      context appears as `foo'.
5587      The expansion depends on the array style user-expand being defined
5588      for the current context; remember that the context for completers
5590      context has not yet been determined.  Elements of the array may
5622 In addition to the context-dependent completions provided, which are
5631      completion bindings in bash.  The last character of the binding
5634      bash, the binding preceded by `\e' gives completion, and preceded
5659      `correct-word' in the FUNCTION field of the context name and then
5673      that invoking _expand_alias once more will expand the now-complete
5678      expand-word command, but using the _expand completer.  Before
5679      calling it, the FUNCTION field of the context is set to
5680      `expand-word'.
5685      the name of the widget in the FUNCTION field of the context and
5697      context in order to change the set of functions used to generate
5751      This widget displays information about the context names, the