fixed ls colors

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

diff --git a/scripts/core/variables.sh b/scripts/core/variables.sh
index 233fadb3b1a5dd1ab6dc0abe66ce6b7ca16c957e..b3119ae55c96e584928a60e47cf417f6e04e4ed9 100644 (file)
--- a/scripts/core/variables.sh
+++ b/scripts/core/variables.sh
@@ -130,7 +130,20 @@ if [ -z "$CORE_VARIABLES_LOADED" ]; then
   fi
   
   ##############
+
+  # set up the color_add variable which is a flag that lets ls know colors work.
+
+  # test if we can use color in ls...
+  ls --help 2>&1 | grep -i -q color
+  if [ $? -eq 0 ]; then
+    export color_add='--color=auto'
+  else
+    export color_add=
+  fi
+  unset test_ls_colors
   
+  ##############
+
   # umask sets a permission mask for all file creations.
   # this mask disallows writes by "group" and "others".
   umask 022
@@ -163,7 +176,7 @@ if [ -z "$CORE_VARIABLES_LOADED" ]; then
       # choose perl's IO over the ms-windows version so we can handle file
       # bytes properly.
   fi
-  
+
   # iterate across our sub-directories and find the perl scripts.
   # this currently only looks one level down.
   for i in $FEISTY_MEOW_SCRIPTS/*; do
@@ -183,8 +196,8 @@ if [ -z "$CORE_VARIABLES_LOADED" ]; then
   # set this so nechung can find its data.
   define_yeti_variable NECHUNG=$FEISTY_MEOW_APEX/infobase/fortunes.dat
   
-  # establish a pipe for less to see our beloved syntax highlighting.
-  define_yeti_variable LESSOPEN="| source-highlight -f esc -o STDOUT -i %s"
+##  # establish a pipe for less to see our beloved syntax highlighting.
+##  define_yeti_variable LESSOPEN="| source-highlight -f esc -o STDOUT -i %s"
 
   # ensure we use the right kind of secure shell.
 #  define_yeti_variable CVS_RSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh