##############
+ORIGINATING_FOLDER="$( \cd "$(\dirname "$0")" && /bin/pwd )"
+CORE_SCRIPTS_DIR="$(echo "$ORIGINATING_FOLDER" | tr '\\\\' '/' )"
+THIS_TOOL_NAME="$(basename "$0")"
+# repair some paths that we should always be able to auto-calculate.
+export FEISTY_MEOW_SCRIPTS="$( \cd "$CORE_SCRIPTS_DIR/.." && /bin/pwd )"
+export FEISTY_MEOW_APEX="$( \cd "$FEISTY_MEOW_SCRIPTS/.." && /bin/pwd )"
+
+##############
+
# some preconditions we want to establish before loading anything...
# make sure that aliases can be used in non-interactive shells.
# 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