mbrubeck / compleat

Generate command-line completions from simple usage descriptions.

This URL has Read+Write access

mbrubeck (author)
Thu Oct 29 06:47:22 -0700 2009
commit  1d58f7bf979d46f6666d1cddc72ab76987824f19
tree    17ea57f71f0d2ec88fc7abbaa5bd4814a69b71d7
parent  0313d3ca33f0b9f448a8f1542d2d06ca80f36c0e
name age message
file .gitignore Sun Oct 25 21:07:26 -0700 2009 Cabal build system. [mbrubeck]
file Completer.hs Loading commit data...
file README.markdown
file Setup.lhs Sun Oct 25 21:07:26 -0700 2009 Cabal build system. [mbrubeck]
file TODO.txt
file Tokenize.hs Thu Oct 29 06:13:22 -0700 2009 More code documentation. [mbrubeck]
file Usage.hs
file compleat.cabal
file compleat.hs Thu Oct 29 06:47:22 -0700 2009 Allow multiple command names per file. [mbrubeck]
file compleat_setup
directory examples/
README.markdown

Compleat

Generate tab completion for any shell command by specifying its usage in a familiar manpage-like format. For example, a usage specification for top(1):

top [-b | -c | -H | -i | -s | -S | -d <delay> | -n <num> | -p <pid> ...] ... ;
top (-h|-v)

The only supported shell at the moment is bash.

Installation

First, install GHC and Parsec. OS X or Windows users, download the Haskell Platform. (Mac OS X 10.6 may require a workaround for 64-bit compatibility.) Debian/Ubuntu users, run: sudo aptitude install libghc6-parsec2-dev

To install Compleat in your system, run:

./Setup.lhs configure
./Setup.lhs build
sudo ./Setup.lhs install

(This will install to /usr/local by default. The "configure" command takes a --prefix=PATH option to change the location, and --user to install as a non-root user.)

To enable compleat in your shell, add the following line to your .bashrc. (Adjust the path if you configured with a custom prefix.)

source /usr/local/share/compleat-1.0/compleat_setup

and install your usage files in a directory named /etc/compleat.d or ~/.compleat:

sudo mkdir /etc/compleat.d
sudo cp examples/* /etc/compleat.d

Restart your shell to begin using completions:

exec bash

Type top or android and then press Tab a few times to see the example files in action.

Syntax

A usage file contains commands and definitions, separated by semicolons.

A command consists of a command name followed by a pattern. The command name can be any atom. If there is more than one command in the file, compleat will attempt to match each of them against the input line.

An atom consists of letters, numbers, and any of the characters -_/@=+.,:, or any string enclosed in double quotes with C/Java-style backslash escapes.

The following are valid patterns:

  • Any atom matches itself: foo matches the string foo. "x\\y" matches the string x\y.
  • a b matches a followed by b.
  • a b | c matches either a b or c.
  • [a] matches zero or more occurrences of a.
  • a ... matches one or more occurrences of a.
  • [a] ... matches zero or more occurrences of a.

Use parentheses to group patterns:

  • a (b | c) matches a followed by either b or c.
  • (a | b) ... matches a or b followed by any number of additional a or b.

Patterns may also include variables:

  • name = value; defines a new variable. The name can be any atom, and the value can be any pattern.
  • <name> in a pattern will be replaced by the value of the name variable. If no value is defined, <name> will match any word.

Copyright

Copyright (c) 2009 Matt Brubeck

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.