cleaning up some too specialized scripts that fred uses.

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

diff --git a/scripts/notes/info_overload_report.sh b/scripts/notes/info_overload_report.sh
index fd4aeb6c2db1498f17801d70ac1ab627e2d850b9..362be0cae33874fa1e7da1a39d2a28fbeb186fd9 100644 (file)
--- a/scripts/notes/info_overload_report.sh
+++ b/scripts/notes/info_overload_report.sh
@@ -98,12 +98,17 @@ full_report+="count\tcomplexity\tweight (kb)\tcategory\n\
 ================================================================\n\
 "
 
+analyze_hierarchy_and_report ~/cloud/urgent "high priority"
+
 # notes are individual files of tasks, usually, although some are combined.
 analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes"
 
 # feisty notes are about feisty meow(r) concerns ltd codebase development.
 analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes"
 
+# home notes are a new top-level category; used to be under the grunty.
+analyze_hierarchy_and_report ~/cloud/branch_road "hearth and home notes"
+
 # scan all the items declared as active projects.
 analyze_by_dir_patterns "active items" ~/cloud/*active*
 
@@ -119,7 +124,7 @@ analyze_hierarchy_and_report ~/cloud/example_source "source examples"
 
 # and then count up the things that we think will be cleaned soon, but one thing we have learned
 # unsorted files haven't been categorized yet.
-analyze_hierarchy_and_report ~/cloud/unsorted "unsorted files"
+analyze_hierarchy_and_report ~/cloud/disordered "unsorted files"
 
 # we now consider the backlog of things to read to be a relevant fact.  this is going to hose
 # up our weight accounting considerably.