boxes.portable 0.0.0 The Boxes Contributors Thomas Jensen

Command Line ASCII Boxes Unlimited!

echo Hello World | boxes` ``` /***************/ /* Hello World */ /***************/ ``` or like this: `C:\>echo Hello World! | boxes -d unicornsay` ``` _______________ / \ | Hello World! | \_________ __'\ |/ \\ \ \\ . |\\/| / " '\ . . . / ) | ' _.' | '-'/ \ ``` A more complex call might look like this: `C:\>echo Spring is in the Air! | boxes -d spring -p h4 -ac` ``` , /\^/`\ | \/ | | | | jgs \ \ / _ _ '\\//' _{ ' }_ || Spring is in the Air! { `.!.` } || ',_/Y\_,' || , {_,_} |\ || |\ | | | || | | (\| /) | | || / / \| // \ \||/ / |// `\\//` \ \./ \\ \./ \\ \./ \ \\ |/ / ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ``` ### Modifying boxes.cfg At some point, you may wish to modify existing box designs or even add your own. When that happens, you may find that you don't have the necessary access permissions to modify boxes.cfg in `%ChocolateyInstall%\lib\boxes.portable\tools` directly. In that case, make a copy of boxes.cfg and place it in one of the precedent locations, where *boxes* finds it before the original. When reading the config file, *boxes* will try these locations (in order): 1. The file specified by the environment variable `BOXES`. 2. A file called boxes.cfg in the directory specified by the environment variable `HOME`. 3. The boxes.cfg installed by choco.   ]]> https://boxes.thomasjensen.com/ ascii ascii-art filter command-line cli https://boxes.thomasjensen.com/images/boxes-sq-256.png https://www.gnu.org/licenses/old-licenses/gpl-2.0.html en false https://boxes.thomasjensen.com/2019/02/boxes-v1.3-released.html https://github.com/ascii-boxes/boxes https://github.com/ascii-boxes/boxes/blob/master/boxes.portable.nuspec https://boxes.thomasjensen.com/docs/ https://github.com/ascii-boxes/boxes/issues