2017-05-05 16:33:21 -05:00
|
|
|
# complete
|
|
|
|
|
2017-05-05 16:39:59 -05:00
|
|
|
[![Build Status](https://travis-ci.org/posener/complete.svg?branch=master)](https://travis-ci.org/posener/complete)
|
2017-05-05 16:47:42 -05:00
|
|
|
[![codecov](https://codecov.io/gh/posener/complete/branch/master/graph/badge.svg)](https://codecov.io/gh/posener/complete)
|
2017-05-06 14:06:49 -05:00
|
|
|
[![GoDoc](https://godoc.org/github.com/posener/complete?status.svg)](http://godoc.org/github.com/posener/complete)
|
|
|
|
[![Go Report Card](https://goreportcard.com/badge/github.com/posener/complete)](https://goreportcard.com/report/github.com/posener/complete)
|
2017-05-05 16:33:21 -05:00
|
|
|
|
2017-05-06 10:55:54 -05:00
|
|
|
A tool for bash writing bash completion in go.
|
2017-05-05 16:33:21 -05:00
|
|
|
|
2017-05-06 10:55:54 -05:00
|
|
|
Writing bash completion scripts is a hard work. This package provides an easy way
|
|
|
|
to create bash completion scripts for any command, and also an easy way to install/uninstall
|
|
|
|
the completion of the command.
|
2017-05-05 16:33:21 -05:00
|
|
|
|
2017-05-06 10:55:54 -05:00
|
|
|
## go command bash completion
|
|
|
|
|
|
|
|
In [gocomplete](./gocomplete) there is an example for bash completion for the `go` command line.
|
|
|
|
|
|
|
|
### Install
|
2017-05-05 16:33:21 -05:00
|
|
|
|
2017-05-06 10:59:06 -05:00
|
|
|
1. Type in your shell:
|
2017-05-05 16:33:21 -05:00
|
|
|
```
|
2017-05-06 10:55:54 -05:00
|
|
|
go get github.com/posener/complete/gocomplete
|
|
|
|
gocomplete -install
|
2017-05-05 16:33:21 -05:00
|
|
|
```
|
|
|
|
|
2017-05-06 10:59:06 -05:00
|
|
|
2. Restart your shell
|
|
|
|
|
2017-05-06 10:55:54 -05:00
|
|
|
### Uninstall
|
2017-05-05 16:33:21 -05:00
|
|
|
|
|
|
|
```
|
2017-05-06 10:55:54 -05:00
|
|
|
gocomplete -uninstall
|
2017-05-05 16:33:21 -05:00
|
|
|
```
|
2017-05-06 14:06:49 -05:00
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
Assuming you have program called `run` and you want to have bash completion
|
|
|
|
for it, meaning, if you type `run` then space, then press the `Tab` key,
|
|
|
|
the shell will suggest relevant complete options.
|
|
|
|
|
|
|
|
In that case, we will create a program called `runcomplete`, a go program,
|
|
|
|
with a `func main()` and so, that will make the completion of the `run`
|
|
|
|
program. Once the `runcomplete` will be in a binary form, we could
|
|
|
|
`runcomplete -install` and that will add to our shell all the bash completion
|
|
|
|
options for `run`.
|
|
|
|
|
|
|
|
So here it is:
|
|
|
|
|
|
|
|
```go
|
|
|
|
import "github.com/posener/complete"
|
|
|
|
|
|
|
|
func main() {
|
|
|
|
|
|
|
|
// create a Command object, that represents the command we want
|
|
|
|
// to complete.
|
|
|
|
run := complete.Command{
|
|
|
|
|
|
|
|
// Name must be exactly as the binary that we want to complete
|
|
|
|
Name: "run",
|
|
|
|
|
|
|
|
// Sub defines a list of sub commands of the program,
|
|
|
|
// this is recursive, since every command is of type command also.
|
|
|
|
Sub: complete.Commands{
|
|
|
|
|
|
|
|
// add a build sub command
|
|
|
|
"build": complete.Command {
|
|
|
|
|
|
|
|
// define flags of the build sub command
|
|
|
|
Flags: complete.Flags{
|
|
|
|
// build sub command has a flag '-fast', which
|
|
|
|
// does not expects anything after it.
|
|
|
|
"-fast": complete.PredictNothing,
|
|
|
|
},
|
|
|
|
},
|
|
|
|
},
|
|
|
|
|
|
|
|
// define flags of the 'run' main command
|
|
|
|
Flags: complete.Flags{
|
|
|
|
|
|
|
|
// a flag '-h' which does not expects anything after it
|
|
|
|
"-h": complete.PredictNothing,
|
|
|
|
|
|
|
|
// a flag -o, which expects a file ending with .out after
|
|
|
|
// it, the tab completion will auto complete for files matching
|
|
|
|
// the given pattern.
|
|
|
|
"-o": complete.PredictFiles("*.out"),
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// run the command completion, as part of the main() function.
|
|
|
|
// this triggers the autocompletion when needed.
|
|
|
|
complete.Run(run)
|
|
|
|
}
|
|
|
|
```
|