updated for new priority folder scheme

[feisty_meow.git] / scripts / agenda / info_overload_report.sh

diff --git a/scripts/agenda/info_overload_report.sh b/scripts/agenda/info_overload_report.sh
index 66d2fbb14ade04ad796967aef6c667ef12216bf0..2179e4005b72c8c44376cbe89d9edda2831810c9 100644 (file)
--- a/scripts/agenda/info_overload_report.sh
+++ b/scripts/agenda/info_overload_report.sh
@@ -118,9 +118,6 @@ full_report+="count\tcomplexity\tweight (kb)\tcategory\n\
 
 #hmmm: don't fail if the hierarchy doesn't exist.
 
-# high priority stuff would be called urgent.
-analyze_hierarchy_and_report $CLOUD_BASE/aaa_priority "high priority (aieeee!)"
-
 # notes are individual files of tasks, usually, although some are combined.
 analyze_hierarchy_and_report $CLOUD_BASE/grunty* "grunty (external facing) notes"
 
@@ -152,6 +149,9 @@ analyze_hierarchy_and_report $CLOUD_BASE/blue_sky "blue sky is the limit ideas"
 # this group is found based on matching a pattern, since we may not use a single
 # standardized name for it, or maybe there are prefixes for similar items (like project-).
 
+# high priority stuff would be called urgent.
+analyze_by_dir_patterns "high priority (aieeee!)" $CLOUD_BASE/*priority*
+
 # scan all the items declared as active projects.
 analyze_by_dir_patterns "active issues" $CLOUD_BASE/*active* 
 
@@ -179,6 +179,9 @@ analyze_by_dir_patterns "jobby work tasks" $CLOUD_BASE/job*
 # scan all the trivial project folders.
 analyze_by_dir_patterns "trivialities and back burner items" $CLOUD_BASE/trivia* $CLOUD_BASE/backburn*
 
+# okay, fudge.  if there are game tasks, then count them too.  what are they, nothing?  not so.
+analyze_by_dir_patterns "play time and games" $CLOUD_BASE/*gaming* $CLOUD_BASE/*game* 
+
 ####
 
 full_report+="================================================================\n\