+ # make sure that aliases can be used in non-interactive shells.
+ shopt -s expand_aliases
+
+ # patch the user variable if we were launched by one of our cron jobs.
+ if [ -z "$USER" -a ! -z "$CRONUSER" ]; then
+ export USER="$CRONUSER"
+ fi
+
+ ##############
+
+ export ERROR_OCCURRED=
+ # there have been no errors to start with, at least. we will set this
+ # to non-empty if something bad happens.
+
+ if [ -z "$FEISTY_MEOW_LOADING_DOCK" ]; then
+ # FEISTY_MEOW_LOADING_DOCK is where the generated files are located.
+ # this is our single entry point we can use without knowing any variables
+ # yet in the initialization process.
+ export FEISTY_MEOW_LOADING_DOCK="$HOME/.zz_feisty_loading"
+ #hmmm: the above is kind of a constant. that's not so great.
+
+ # make sure our main variables are established.
+ FEISTY_MEOW_VARIABLES_LOADING_FILE="$FEISTY_MEOW_LOADING_DOCK/fmc_variables.sh"
+ if [ ! -f "$FEISTY_MEOW_VARIABLES_LOADING_FILE" ]; then
+ echo -e "\
+
+ The feisty meow scripts need initialization via the bootstrap process. For\n\
+ example, if the feisty meow folder lives in '$DEFAULT_FEISTYMEOW_ORG_DIR', then this\n\
+ command bootstraps feisty meow:\n\
+ \n\
+ bash $example_dir/feisty_meow/scripts/core/reconfigure_feisty_meow.sh\n\
+ \n\
+ \n"
+ ERROR_OCCURRED=true
+ fi
+
+ ##############
+
+ if [ -z "$ERROR_OCCURRED" ]; then