mongo's quest for relevance


YETIcode

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 feistymeow.org for more details.

Download:
The final (probably) yeti package: YETIcode v.[an error occurred while processing this directive]
packaged on [an error occurred while processing this directive]

YETI contains the following collections:

Setting up the Yeti: A Quick Start Guide in Four Steps (and a few sub-steps)

  1. Get the YETIcode archive:
    1. Option A: See way above for download link and unpack the archive to your ~/yeti folder.
    2. Option B: Get YETI through svn at SourceForge:
      1. svn checkout svn://svn.code.sf.net/p/yeti/svn/yeti
  2. Initialize the YETI support:
    1. If you're running on Windows with msys, ensure the msys bin directory is in your path, e.g.:  export PATH=/bin:$PATH
    2. bash ~/yeti/scripts/core/bootstrap_shells.sh
  3. Hook up the yeti scripts: (enter the text lines verbatim)
    1. Option A: Activate yeti automatically on shell startup (please do not do this for root):
      vi ~/.bashrc
      G
      :r ~/yeti/scripts/examples/bashrc_user
      :wq
    2. Option B: Turn yeti on only when the yetime alias is invoked (it's okay for root to have this):
      vi ~/.bashrc
      G
      :r ~/yeti/scripts/examples/bashrc_root
      :wq

  4. Restart your shell environment (exit the bash prompt):
    1. Once you log out and log back in, the updated aliases and variables in the yeti startup scripts should be in effect.
    2. If you chose approach 3.2 above, then entering the command "yetime" will enable all the aliases.

#[an error occurred while processing this directive]