- I think it would be better if one for commands only, one for the spec handling core logic so people won't be confused by the core logic inside the commands folder (cleaner I guess) - Regen docs
21 lines
809 B
Go
21 lines
809 B
Go
package sys
|
|
|
|
import (
|
|
"github.com/versenilvis/iris/spec"
|
|
)
|
|
|
|
func init() {
|
|
spec.Register(&spec.Spec{
|
|
Name: "where",
|
|
Description: "For each name, indicate how it should be interpreted",
|
|
Options: []spec.Option{
|
|
{Name: "-w", Description: "For each name, print 'name: word', where 'word' is the kind of command"},
|
|
{Name: "-p", Description: "Do a path search for the name, even if it's an alias/function/builtin"},
|
|
{Name: "-m", Description: "The arguments are taken as patterns (pattern characters must be quoted)"},
|
|
{Name: "-s", Description: "If the pathname contains symlinks, print the symlink-free name as well"},
|
|
{Name: "-S", Description: "Print intermediate symlinks and the resolved name"},
|
|
{Name: "-x", Description: "Expand tabs when outputting shell function"},
|
|
},
|
|
})
|
|
}
|