Bash Completions
You can enable built-in bash completion support by setting the EnableBashCompletion field on your cli.App to true. This automatically provides completion suggestions for your app's subcommands. You can also define custom completion logic for specific commands or flags.
Default auto-completion¶
package main
import (
"fmt"
"log"
"os"
"github.com/aperturerobotics/cli"
)
func main() {
app := &cli.App{
EnableBashCompletion: true,
Commands: []*cli.Command{
{
Name: "add",
Aliases: []string{"a"},
Usage: "add a task to the list",
Action: func(cCtx *cli.Context) error {
fmt.Println("added task: ", cCtx.Args().First())
return nil
},
},
{
Name: "complete",
Aliases: []string{"c"},
Usage: "complete a task on the list",
Action: func(cCtx *cli.Context) error {
fmt.Println("completed task: ", cCtx.Args().First())
return nil
},
},
{
Name: "template",
Aliases: []string{"t"},
Usage: "options for task templates",
Subcommands: []*cli.Command{
{
Name: "add",
Usage: "add a new template",
Action: func(cCtx *cli.Context) error {
fmt.Println("new task template: ", cCtx.Args().First())
return nil
},
},
{
Name: "remove",
Usage: "remove an existing template",
Action: func(cCtx *cli.Context) error {
fmt.Println("removed task template: ", cCtx.Args().First())
return nil
},
},
},
},
},
}
if err := app.Run(os.Args); err != nil {
log.Fatal(err)
}
}
Custom auto-completion¶
package main
import (
"fmt"
"log"
"os"
"github.com/aperturerobotics/cli"
)
func main() {
tasks := []string{"cook", "clean", "laundry", "eat", "sleep", "code"}
app := &cli.App{
EnableBashCompletion: true,
Commands: []*cli.Command{
{
Name: "complete",
Aliases: []string{"c"},
Usage: "complete a task on the list",
Action: func(cCtx *cli.Context) error {
fmt.Println("completed task: ", cCtx.Args().First())
return nil
},
BashComplete: func(cCtx *cli.Context) {
// This will complete if no args are passed
if cCtx.NArg() > 0 {
return
}
for _, t := range tasks {
fmt.Println(t)
}
},
},
},
}
if err := app.Run(os.Args); err != nil {
log.Fatal(err)
}
}
Enabling¶
To enable auto-completion for your application in the current shell session, you can use the autocomplete/bash_autocomplete script provided in the aperturerobotics/cli repository.
The
bash-completionpackage or equivalent that provides the_get_comp_words_by_reffunction for the target platform must be installed and initialized for this completion script to work correctly.
First, set the PROG environment variable to the name of your compiled application binary. Then, source the autocomplete/bash_autocomplete script:
For example, if your cli program is called myprogram:
$ PROG=myprogram source path/to/cli/autocomplete/bash_autocomplete
Auto-completion is now enabled for the current shell, but will not persist into a new shell.
Distribution and Persistent Autocompletion¶
To make autocompletion persistent across shell sessions, you have a few options:
- System-wide Installation: Copy
autocomplete/bash_autocompleteto/etc/bash_completion.d/and rename it to match your program's name (e.g.,/etc/bash_completion.d/myprogram). This is common when distributing packages. Users may need to restart their shell or source the file manually (source /etc/bash_completion.d/<myprogram>) for the changes to take effect immediately.
$ sudo cp path/to/autocomplete/bash_autocomplete /etc/bash_completion.d/<myprogram>
$ source /etc/bash_completion.d/<myprogram>
- User Configuration: Instruct users to add the following lines to their shell configuration file (e.g.,
~/.bashrcor~/.bash_profile), ensuring they replace<myprogram>with the actual program name andpath/to/cliwith the correct path to the script:
$ PROG=<myprogram>
$ source path/to/cli/autocomplete/bash_autocomplete
Keep in mind that if they are enabling auto-completion for more than one
program, they will need to set PROG and source
autocomplete/bash_autocomplete for each program, like so:
$ PROG=<program1>
$ source path/to/cli/autocomplete/bash_autocomplete
$ PROG=<program2>
$ source path/to/cli/autocomplete/bash_autocomplete
Customization¶
The default shell completion flag (--generate-bash-completion) is defined as
cli.EnableBashCompletion, and may be redefined if desired, e.g.:
package main
import (
"log"
"os"
"github.com/aperturerobotics/cli"
)
func main() {
app := &cli.App{
EnableBashCompletion: true,
Commands: []*cli.Command{
{
Name: "wat",
},
},
}
if err := app.Run(os.Args); err != nil {
log.Fatal(err)
}
}
ZSH Support¶
Auto-completion for ZSH is also supported using the
autocomplete/zsh_autocomplete file included in this repo. One environment
variable is used, PROG. Set PROG to the program name as before, and then
source path/to/autocomplete/zsh_autocomplete. Adding the following lines to
your ZSH configuration file (usually .zshrc) will allow the auto-completion to
persist across new shells:
$ PROG=<myprogram>
$ source path/to/autocomplete/zsh_autocomplete
ZSH default auto-complete example¶

ZSH custom auto-complete example¶

PowerShell Support¶
Auto-completion for PowerShell is also supported using the
autocomplete/powershell_autocomplete.ps1 file included in this repo.
Rename the script to <my program>.ps1 and move it anywhere in your file
system. The location of script does not matter, only the file name of the
script has to match the your program's binary name.
To activate it, enter:
& path/to/autocomplete/<my program>.ps1
To persist across new shells, open the PowerShell profile (with code $profile
or notepad $profile) and add the line:
& path/to/autocomplete/<my program>.ps1