From ced9f74c3496cab0d469b7fa15637f589af466b1 Mon Sep 17 00:00:00 2001
From: Alain Reguera Delgado <alain.reguera@gmail.com>
Date: Oct 31 2010 09:46:53 +0000
Subject: Update AsToKnowMoreLine inside cli_printMessage.sh. 


    - When building documentation entries from caller's output, do not
      build documentation entries for repository files. Instead, build
      documentation entries for their parent directory.

    - At this moment I don't see a reason to create file-specific
      documentation entries. Most file-specific documentation can be
      organized in their parent directory documentation entry.

    - Consistency is another issue. Not all repository files need to
      be documented. Nevertheless, all repository directories do need
      to be documented.


---

diff --git a/Scripts/Bash/Functions/cli_printMessage.sh b/Scripts/Bash/Functions/cli_printMessage.sh
index 271943a..06e857a 100755
--- a/Scripts/Bash/Functions/cli_printMessage.sh
+++ b/Scripts/Bash/Functions/cli_printMessage.sh
@@ -136,11 +136,8 @@ function cli_printMessage {
         'AsToKnowMoreLine' )
             # This option receives the output of bash's caller builtin
             # as message value, in order to produce the documentation
-            # entry automatically. As caller builtin outputs the
-            # caller file path, documentation entry built from here is
-            # a file documentation entry.
-            MESSAGE=$(echo $MESSAGE | cut -d ' ' -f2-)
-            MESSAGE="$(dirname $MESSAGE)' --filter='$(basename $MESSAGE)"
+            # entry automatically. 
+            MESSAGE=$(dirname $(echo $MESSAGE | cut -d ' ' -f2-))
             echo "----------------------------------------------------------------------"
             echo "`gettext "To know more, run the following command"`:"
             echo "centos-art help --read='$MESSAGE'"