Makes command-line tools easier to use through implicit option files.
Advantages over adding
- folder specific options
- easier format for reading, editing, and sharing
- comments on options
Only disadvantages I can see compared to adding
alias is the need to
install stuff. But then I'm biased. :-)
I'm just getting started so do not consider anything bolted down until
version is at least
npm install -g wiz
Create a custom version of
ack command named
wiz curry ack # creates ~/.wiz/bin/zack  wiz link zack # creates /usr/local/bin/zack -> ~/.wiz/bin/zack 
wiz currycommand didn't provide a name for the custom command, default name with
zprefix is used.
wiz linkstep is unnecessary if you have
Create an option file for
Option file for
zack must be named
zack.opts and may be located in any
directories between current working directory and
HOME directory. Option
file may also be stored in each directory's
Directories searched when current working directory is
/Users/don/github/wiz /Users/don/github/wiz/.wiz /Users/don/github /Users/don/github/.wiz /Users/don /Users/don/.wiz
-i --ignore-dir node_modules # this requires ack 2.0 --nojs
Option lines starting with
# in option files are ignored.
This command line is equivalent to:
ack -i --ignore-dir node_modules --nojs hello
Create another version of
ack for just searching css files
Full syntax of
wiz curry command is
wiz curry <target-command> [<curry-cmd>]
<curry-cmd> is target command name prefixed with
Example creating a curry command with non-default name
wiz curry ack ackcss
ackcss will use option files named
ackcss.opts if exists
wiz unlink zack
Developed and tested on OS X.
Should not have issues with Linux except for
wiz link command.
Windows is currently not supported. Hope to address this at some point. Any help in this regard is welcome.
wiz has issues with interactive command-line tools and tools
that behaves differently based on whether
stdin is TTY or not.
In case of
ag which falls in the second category, add