##############
-# SHELL_DEBUG: if this variable is non-empty, then it causes the feisty meow
+# DEBUG_FEISTY_MEOW: if this variable is non-empty, then it causes the feisty meow
# scripts to print more diagnostic information when they run. not all
# scripts support this, but the core ones do.
-#export SHELL_DEBUG=true
+#export DEBUG_FEISTY_MEOW=true
+
+##############
+
+# this script cannot handle figuring out where it lives, so approaches that
+# get the WORKDIR will fail. this is a consequence of this always being used
+# in bash's 'source' directive, which does not pass the script name as
+# argument 0. instead, we just check for the bad condition of a malconfigured
+# script system and try to repair it.
+
+# check if any crucial folder is hosed. we will torch the existing config
+# to the extent we can.
+if [ ! -d "$FEISTY_MEOW_SCRIPTS" -o ! -d "$FEISTY_MEOW_APEX" ]; then
+ # wipe out the offending variable(s).
+ unset FEISTY_MEOW_SCRIPTS FEISTY_MEOW_APEX
+ # clean out any unfortunate wrongness that may exist in our generated areas.
+ if [ -d "$"FEISTY_MEOW_LOADING_DOCK ]; then \rm -rf "$FEISTY_MEOW_LOADING_DOCK"; fi
+ if [ -d "$FEISTY_MEOW_GENERATED_STORE" ]; then \rm -rf "$FEISTY_MEOW_GENERATED_STORE"; fi
+ # also wipe any values from the variables pointing at generated stuff.
+ unset FEISTY_MEOW_LOADING_DOCK FEISTY_MEOW_GENERATED_STORE
+ exec "$*"
+fi
##############
# 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 '\n\n'
echo -e "\
-The feisty meow scripts need initialization via the bootstrap process, which\n\
-can be accomplished if one knows where the scripts are stored. For example,\n\
-if feisty_meow is in the home directory, then this command will bootstrap the\n\
-script configuration:\n\
-\n\
- bash $HOME/feisty_meow/scripts/core/reconfigure_feisty_meow.sh\n\
+
+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\
-Or, if the feisty_meow folder is installed system-wide in a location such as\n\
-/usr/local/feisty_meow, then this command would bootstrap the scripts:\n\
+ bash $example_dir/feisty_meow/scripts/core/reconfigure_feisty_meow.sh\n\
\n\
- bash /usr/local/feisty_meow/scripts/core/reconfigure_feisty_meow.sh\n\
\n"
ERROR_OCCURRED=true
fi
# perform the bulkier parts of the initialization process.
- if [ ! -z "$SHELL_DEBUG" ]; then echo "heavyweight init begins..."; fi
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then echo "heavyweight init begins..."; fi
# set up the aliases for the shell, but only if they are not already set.
type CORE_ALIASES_LOADED &>/dev/null
if [ $? -ne 0 ]; then
- if [ ! -z "$SHELL_DEBUG" ]; then
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then
echo "the aliases were missing, now they are being added..."
fi
source "$FEISTY_MEOW_LOADING_DOCK/fmc_core_and_custom_aliases.sh"
# a minor tickle of the title of the terminal, unless we already have some history.
label_terminal_with_info
- if [ ! -z "$SHELL_DEBUG" ]; then echo "heavyweight init is done."; fi
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then echo "heavyweight init is done."; fi
if [ -z "$ERROR_OCCURRED" ]; then
# set a sentinel variable to say we loaded the feisty meow environment.