very sweet auto-location working

[feisty_meow.git] / scripts / core / launch_feisty_meow.sh

diff --git a/scripts/core/launch_feisty_meow.sh b/scripts/core/launch_feisty_meow.sh
index b9ba1d72979fa2818e23aab1698eb07f5e7bf29f..496786a71dcb6fbf6201068f93b6be4b34a591c8 100644 (file)
--- a/scripts/core/launch_feisty_meow.sh
+++ b/scripts/core/launch_feisty_meow.sh
@@ -10,11 +10,20 @@
 
 ##############
 
-# 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
+
+##############
+
+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 )"
 
 ##############
 
@@ -44,19 +53,14 @@ if [ -z "$FEISTY_MEOW_LOADING_DOCK" ]; then
   # 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
@@ -120,12 +124,12 @@ if [ -z "$ERROR_OCCURRED" ]; then
   
   # 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"
@@ -137,7 +141,7 @@ if [ -z "$ERROR_OCCURRED" ]; then
   # 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.