Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Contact Us
Online Help
Domain Status
Man Pages

Virtual Servers

Topology Map

Server Agreement
Year 2038

USA Flag



Man Pages

Manual Reference Pages  -  PSHCOMPLETE (1)

.ds Aq ’


pshcomplete - TAB completion in Perl Shell



TAB completion strategies in Perl Shell


<B>pshB> supports built-in completion support as well as a largely <B>bashB> compatible user-programmable completion.

Whenever a user presses the TAB key, <B>pshB> first checks wether we’re trying to complete a command for which there’s a user-programmed completion. Please see below for further information about this process.

If there are no user-programmed completions, following default completion strategies are checked in the specified order:
Perl Hash Keys If the current expression looks like an attempt to enter the key of a Perl Hash ( $var{$keypart or $var-{$keypart> ), <B>pshB> will examine the Perl symbol table to try to complete the entered key.
Perl Methods Afterwards <B>pshB> will try to complete method calls which look like $obj-methodpart>.
Perl Variables An attempt is then made to complete any perl variable names starting with one the most usual context signifiers ( @$%& or $# ).
Executables If the user is currently working on the first word of the line or a similar syntactic position (like the first word after a pipe sign), <B>pshB> attempts to find an executable in the current path matching the expression.
Filenames If no completions could be generated so far, <B>pshB> will attempt to complete the word as a filename.
Built-ins Afterwards, <B>pshB> will check wether the command to execute is a builtin command. If yes, the builtin command is asked for a list of completions. The list of completions supplied by the builtin may or may not replace the list of so far gathered possible completions, depending on the builtin.



This Psh::PCompletion module provides the programmable completion function almost compatible with the one of bash-2.04 and/or later. The following document is based on the texinfo file of bash-2.04-beta5.

    Programmable Completion

When word completion is attempted for an argument to a command for which a completion specification (a COMPSPEC) has been defined using the <B>completeB> builtin (See Programmable Completion Builtins.), the programmable completion facilities are invoked.

First, the command name is identified. If a compspec has been defined for that command, the compspec is used to generate the list of possible completions for the word. If the command word is a full pathname, a compspec for the full pathname is searched for first. If no compspec is found for the full pathname, an attempt is made to find a compspec for the portion following the final slash.

Once a compspec has been found, it is used to generate the list of matching words. If a compspec is not found, the default Psh completion described above (Where is it described?) is performed.

First, the actions specified by the compspec are used. Only matches which are prefixed by the word being completed are returned. When the <B>-fB> or <B>-dB> option is used for filename or directory name completion, the shell variable <B>FIGNOREB> is used to filter the matches. See ENVIRONMENT VARIABLES for a description of <B>FIGNOREB>.

Any completions specified by a filename expansion pattern to the <B>-GB> option are generated next. The words generated by the pattern need not match the word being completed. The <B>GLOBIGNOREB> shell variable is not used to filter the matches, but the <B>FIGNOREB> shell variable is used.

Next, the string specified as the argument to the <B>-WB> option is considered. The string is first split using the characters in the <B>IFSB> special variable as delimiters. Shell quoting is honored. Each word is then expanded using brace expansion, tilde expansion, parameter and variable expansion, command substitution, arithmetic expansion, and pathname expansion, as described above (Where is it described?). The results are split using the rules described above (Where is it described?). No filtering against the word being completed is performed.

After these matches have been generated, any shell function or command specified with the <B>-FB> and <B>-CB> options is invoked. When the function or command is invoked, the first argument is the word being completed, the second argument is the current command line, the third argument is the index of the current cursor position relative to the beginning of the current command line, and the fourth argument is the name of the command whose arguments are being completed. If the current cursor position is at the end of the current command, the value of the third argument is equal to the length of the second argument string.

No filtering of the generated completions against the word being completed is performed; the function or command has complete freedom in generating the matches.

Any function specified with <B>-FB> is invoked first. The function may use any of the shell facilities, including the <B>compgenB> builtin described below (See Programmable Completion Builtins.), to generate the matches. It returns a array including the possible completions. For example;

        sub _foo_func {
            my ($cur, $line, $start, $cmd) = @_;
            return @possible_completions;
        complete -F _foo_func bar

Next, any command specified with the <B>-CB> option is invoked in an environment equivalent to command substitution. It should print a list of completions, one per line, to the standard output. Backslash may be used to escape a newline, if necessary.

After all of the possible completions are generated, any filter specified with the <B>-XB> option is applied to the list. The filter is a pattern as used for pathname expansion; a & in the pattern is replaced with the text of the word being completed. A literal & may be escaped with a backslash; the backslash is removed before attempting a match. Any completion that matches the pattern will be removed from the list. A leading ! negates the pattern; in this case any completion not matching the pattern will be removed.

Finally, any prefix and suffix specified with the <B>-PB> and <B>-SB> options are added to each member of the completion list, and the result is returned to the Readline completion code as the list of possible completions.

If a compspec is found, whatever it generates is returned to the completion code as the full set of possible completions. The default Bash completions are not attempted, and the Readline default of filename completion is disabled.

    Programmable Completion Builtins

A builtin commands <B>completeB> and a builtin Perl function <B>compgenB> are available to manipulate the programmable completion facilities.

        compgen [OPTION] [WORD]

Generate possible completion matches for WORD according to the OPTIONs, which may be any option accepted by the <B>completeB> builtin with the exception of <B>-pB> and <B>-rB>, and write the matches to the standard output. When using the <B>-FB> or <B>-CB> options, the various shell variables set by the programmable completion facilities, while available, will not have useful values.

The matches will be generated in the same way as if the programmable completion code had generated them directly from a completion specification with the same flags. If WORD is specified, only those completions matching WORD will be displayed.

The return value is true unless an invalid option is supplied, or no matches were generated.


        complete [-abcdefjkvu] [-A ACTION] [-G GLOBPAT] [-W WORDLIST]
                 [-P PREFIX] [-S SUFFIX] [-X FILTERPAT] [-x FILTERPAT]
                 [-F FUNCTION] [-C COMMAND] NAME [NAME ...]
        complete -pr [NAME ...]

Specify how arguments to each NAME should be completed. If the <B>-pB> option is supplied, or if no options are supplied, existing completion specifications are printed in a way that allows them to be reused as input. The <B>-rB> option removes a completion specification for each NAME, or, if no NAMEs are supplied, all completion specifications.

The process of applying these completion specifications when word completion is attempted is described above (See Programmable Completion.).

Other options, if specified, have the following meanings. The arguments to the <B>-GB>, <B>-WB>, and <B>-XB> options (and, if necessary, the <B>-PB> and <B>-SB> options) should be quoted to protect them from expansion before the <B>completeB> builtin is invoked.
<B>-AB> ACTION The ACTION may be one of the following to generate a list of possible completions:
<B>aliasB> Alias names. May also be specified as <B>-aB>.
<B>arrayvarB> Names of Perl array variable names.
<B>bindingB> Readline key binding names.
<B>builtinB> Names of shell builtin commands. May also be specified as <B>-bB>.
<B>commandB> Command names. May also be specified as <B>-cB>.
<B>directoryB> Directory names. May also be specified as <B>-dB>.
<B>disabledB> Names of disabled shell builtins (not implemented yet.).
<B>enabledB> Names of enabled shell builtins (not implemented yet.).
<B>exportB> Names of exported shell variables. May also be specified as <B>-eB>.
<B>fileB> File names. May also be specified as <B>-fB>.
<B>functionB> Names of Perl functions.
<B>hashvarB> Names of Perl hash variable names.
<B>helptopicB> Help topics as accepted by the ‘help’ builtin.
<B>hostnameB> Hostnames.
<B>jobB> Job names, if job control is active. May also be specified as <B>-jB>.
<B>keywordB> Shell reserved words. May also be specified as <B>-kB>.
<B>runningB> Names of running jobs, if job control is active.
<B>setoptB> Valid arguments for the <B>-oB> option to the <B>setB> builtin (not implemented yet.).
<B>shoptB> Shell option names as accepted by the <B>shoptB> builtin (not implemented yet.).
<B>signalB> Signal names.
<B>stoppedB> Names of stopped jobs, if job control is active.
<B>userB> User names. May also be specified as <B>-uB>.
<B>variableB> Names of all Perl variables. May also be specified as <B>-vB>.
<B>-GB> GLOBPAT The filename expansion pattern GLOBPAT is expanded to generate the possible completions.
<B>-WB> WORDLIST The WORDLIST is split using the characters in the <B>IFSB> special variable as delimiters, and each resultant word is expanded. The possible completions are the resultant list.
<B>-CB> COMMAND COMMAND is executed in a subshell environment, and its output is used as the possible completions.
<B>-FB> FUNCTION The shell function FUNCTION is executed in the current Perl shell environment. When it finishes, the possible completions are retrieved from the array which the function returns.
<B>-XB> FILTERPAT FILTERPAT is a pattern as used for filename expansion. It is applied to the list of possible completions generated by the preceding options and arguments, and each completion matching FILTERPAT is removed from the list. A leading ! in FILTERPAT negates the pattern; in this case, any completion not matching FILTERPAT is removed.
<B>-xB> FILTERPAT Similar to the <B>-XB> option above, except it is applied to only filenames not to directory names etc.
<B>-PB> PREFIX PREFIX is added at the beginning of each possible completion after all other options have been applied.
<B>-SB> SUFFIX SUFFIX is appended to each possible completion after all other options have been applied.

The return value is true unless an invalid option is supplied, an option other than <B>-pB> or <B>-rB> is supplied without a NAME argument, an attempt is made to remove a completion specification for a NAME for which no specification exists, or an error occurs adding a completion specification.


Hiroo Hayashi,


info manual of bash-2.04 and/or later


complete_example in the Psh distribution shows you many examples of the usage of programmable completion.

        source complete-examples


Copyright (C) 1999-2003 Gregor N. Purdy. All rights reserved. This script is free software. It may be copied or modified according to the same terms as Perl itself.
Search for    or go to Top of page |  Section 1 |  Main Index

perl v5.20.3 PSHCOMPLETE (1) 2007-07-06

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.