Free Scripts and Dubious Miscellany
NOTE: yeti is now at final release.
As of January 14th 2012, yeti and yeticode.org are now retired software.
The revision control systems will continue to operate, but this product has been mothballed.
For the new and improved and different product line that will continue, please see
for more details.
YETI contains the following collections:
Setting up the Yeti: A Quick
Guide in Four Steps (and a few sub-steps)
- Get the YETIcode archive:
- Option A: See way above for download link and unpack the
archive to your ~/yeti folder.
- Option B: Get YETI through svn at SourceForge:
- svn checkout svn://svn.code.sf.net/p/yeti/svn/yeti
- Initialize the YETI support:
If you're running on Windows with msys, ensure the msys bin directory is
in your path, e.g.: export PATH=/bin:$PATH
- bash ~/yeti/scripts/core/bootstrap_shells.sh
- Hook up the yeti scripts: (enter the text lines verbatim)
- Option A: Activate yeti automatically on shell startup
(please do not do
- Option B: Turn yeti on only when the yetime alias is
invoked (it's okay for root to have this):
- Restart your shell environment (exit the bash prompt):
- Once you log out and log back in, the updated
variables in the yeti startup scripts should be in effect.
- If you chose approach 3.2 above, then entering the
command "yetime" will enable all the aliases.
#[an error occurred while processing this directive]