+ exec bash -i 3<<EOF 4<&0 <&3
+ echo -e '\n\n^^^ errors above here indicate potential problems in .bashrc ^^^';
+ export FEISTY_MEOW_APEX=\"\$(pwd)\"; export FEISTY_MEOW_SCRIPTS=\$FEISTY_MEOW_APEX/scripts;
+ export FEISTY_MEOW_SHOW_LAUNCH_GREETING=yes;
+ /bin/bash \$(pwd)/scripts/core/reconfigure_feisty_meow.sh;
+ source \$(pwd)/scripts/core/launch_feisty_meow.sh; exec 3>&- <&4
+EOF
+##############
+
+
+This code snippet assumes that the .bashrc file could still need editing to
+fix an erroneous FEISTY_MEOW_APEX variable, so we skip it above when bash
+runs. Check \$HOME/.bashrc to see if a change there will fix the problem.
+
+"
+else
+ # apex is good, so let's make the scripts good too.
+ if [ -z "$FEISTY_MEOW_SCRIPTS" -o ! -d "$FEISTY_MEOW_SCRIPTS" ]; then
+ export FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_APEX/scripts"
+ fi
+ # check again to test our belief system...
+ if [ ! -d "$FEISTY_MEOW_SCRIPTS" ]; then
+ unset NO_REPAIRS_NEEDED
+ echo -e "The feisty meow scripts cannot be found under the current top:\n FEISTY_MEOW_APEX=$FEISTY_MEOW_APEX"
+ fi
+fi
+
+if [ "$NO_REPAIRS_NEEDED" == "true" ]; then
+
+ # we believe it's safe to run through the rest of this script.
+
+ ##############
+
+ # some preconditions we want to establish before loading anything...
+
+ # 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.