Rename org-gtd-review.el to org-gtd-reflect.el

CHANGELOG.org

@@ -1,3 +1,12 @@
+* 3.1.0 (unstable)
+** Fix edge case of processing empty heading ( #169 )
+** Better messages in minibuffer
+- discover ~with-temp-message~ to hide things we don't care about.
+** Adding task to a project works ( #160 )
+- Now uses org-refile like it was meant to be used
+- Now works for projects outside ~org-gtd-directory~.
+** Better alignment with step names used by David Allen
+- File org-gtd-review.el renamed to org-gtd-reflect.el
 * 3.0.0
 ** Functions exist to create your own hooks
 Make GTD truly a part of your emacs experience.

README.org

@@ -57,11 +57,11 @@ Hooks:
 Functions:
 - ~org-gtd-engage~ :: Your daily view.
 - ~org-gtd-engage-grouped-by-context~ :: All NEXT actions, grouped by tags beginning with =@=. This may not work if you remove ~org-set-tags-command~ from ~org-gtd-organize-hooks~.
-*** GTD Step 6/6 : Review
+*** GTD Step 6/6 : Reflect
 Functions:
 - ~org-gtd-oops~ :: Show all the missed appointments. Oops!
-- ~org-gtd-review-area-of-focus~ :: Show an agenda view designed for one of your areas of focus.
-- ~org-gtd-review-stuck-*~ :: The =*= here is any of the action types; you can find any of the ones that have fallen through the cracks.
+- ~org-gtd-reflect-area-of-focus~ :: Show an agenda view designed for one of your areas of focus.
+- ~org-gtd-reflect-stuck-*~ :: The =*= here is any of the action types; you can find any of the ones that have fallen through the cracks.
 
 
 * Directory tree

doc/org-gtd.org

@@ -524,7 +524,7 @@ If you are a Doom Emacs user, then your configuration may look something like th
            :desc "Engage"         "e"  #'org-gtd-engage
            :desc "Process inbox"  "p"  #'org-gtd-process-inbox
            :desc "Show all next"  "n"  #'org-gtd-show-all-next
-           :desc "Stuck projects" "s"  #'org-gtd-review-stuck-projects))
+           :desc "Stuck projects" "s"  #'org-gtd-reflect-stuck-projects))
     (map! :map org-gtd-clarify-map
           :desc "Organize this item" "C-c c" #'org-gtd-organize))
 #+END_SRC
@@ -704,7 +704,7 @@ Horizon 2 is now handled by a variable and a hook you can add to ~org-gtd-organi
 - ~org-gtd-areas-of-focus~ is a list of strings, each representing one of your areas of focus.
 - ~org-gtd-set-area-of-focus~ is the hook you would add, e.g. ~(setq org-gtd-organize-hooks '(org-gtd-set-area-of-focus))~, it ensures each item you clarify will need to be part of a horizon.
 
-You can then use the function ~org-gtd-review-area-of-focus~ to generate an agenda view to review a specific area of focus.
+You can then use the function ~org-gtd-reflect-area-of-focus~ to generate an agenda view to review a specific area of focus.
 
 In order to add areas of focus to pre-existing items in your system, without going through the clarifying flow, we provide two functions:
 - ~org-gtd-area-of-focus-set-on-item-at-point~, when you are on a org heading
@@ -790,12 +790,12 @@ For instance, one way this could work:
 ** Finding lost tasks
 Sometimes things break. The following functions will help you find these items:
 
-- ~org-gtd-review-stuck-calendar-items~
-- ~org-gtd-review-stuck-incubated-items~
-- ~org-gtd-review-stuck-habit-items~
-- ~org-gtd-review-stuck-delegated-items~
-- ~org-gtd-review-stuck-single-action-items~
-- ~org-gtd-review-stuck-projects~
+- ~org-gtd-reflect-stuck-calendar-items~
+- ~org-gtd-reflect-stuck-incubated-items~
+- ~org-gtd-reflect-stuck-habit-items~
+- ~org-gtd-reflect-stuck-delegated-items~
+- ~org-gtd-reflect-stuck-single-action-items~
+- ~org-gtd-reflect-stuck-projects~
 
 ** Projects without a NEXT item
 

doc/org-gtd.texi

@@ -907,7 +907,7 @@ If you are a Doom Emacs user, then your configuration may look something like th
          :desc "Engage"         "e"  #'org-gtd-engage
          :desc "Process inbox"  "p"  #'org-gtd-process-inbox
          :desc "Show all next"  "n"  #'org-gtd-show-all-next
-         :desc "Stuck projects" "s"  #'org-gtd-review-stuck-projects))
+         :desc "Stuck projects" "s"  #'org-gtd-reflect-stuck-projects))
   (map! :map org-gtd-clarify-map
         :desc "Organize this item" "C-c c" #'org-gtd-organize))
 @end lisp
@@ -1190,7 +1190,7 @@ Horizon 2 is now handled by a variable and a hook you can add to @code{org-gtd-o
 @code{org-gtd-set-area-of-focus} is the hook you would add, e.g. @code{(setq org-gtd-organize-hooks '(org-gtd-set-area-of-focus))}, it ensures each item you clarify will need to be part of a horizon.
 @end itemize
 
-You can then use the function @code{org-gtd-review-area-of-focus} to generate an agenda view to review a specific area of focus.
+You can then use the function @code{org-gtd-reflect-area-of-focus} to generate an agenda view to review a specific area of focus.
 
 In order to add areas of focus to pre-existing items in your system, without going through the clarifying flow, we provide two functions:
 @itemize
@@ -1315,17 +1315,17 @@ Sometimes things break. The following functions will help you find these items:
 
 @itemize
 @item
-@code{org-gtd-review-stuck-calendar-items}
+@code{org-gtd-reflect-stuck-calendar-items}
 @item
-@code{org-gtd-review-stuck-incubated-items}
+@code{org-gtd-reflect-stuck-incubated-items}
 @item
-@code{org-gtd-review-stuck-habit-items}
+@code{org-gtd-reflect-stuck-habit-items}
 @item
-@code{org-gtd-review-stuck-delegated-items}
+@code{org-gtd-reflect-stuck-delegated-items}
 @item
-@code{org-gtd-review-stuck-single-action-items}
+@code{org-gtd-reflect-stuck-single-action-items}
 @item
-@code{org-gtd-review-stuck-projects}
+@code{org-gtd-reflect-stuck-projects}
 @end itemize
 
 @node Projects without a NEXT item