Browse Source

org.texi: Clarify documentation regarding TODO state change logging.

Jason Dunsmore 13 years ago
parent
commit
3e6ac9dfe2
1 changed files with 6 additions and 2 deletions
  1. 6 2
      doc/org.texi

+ 6 - 2
doc/org.texi

@@ -4032,14 +4032,18 @@ also overrule the setting of this variable for a subtree by setting a
 
 
 Since it is normally too much to record a note for every state, Org-mode
 Since it is normally too much to record a note for every state, Org-mode
 expects configuration on a per-keyword basis for this.  This is achieved by
 expects configuration on a per-keyword basis for this.  This is achieved by
-adding special markers @samp{!} (for a timestamp) and @samp{@@} (for a note)
-in parentheses after each keyword.  For example, with the setting
+adding special markers @samp{!} (for a timestamp) or @samp{@@} (for a note
+with timestamp) in parentheses after each keyword.  For example, with the
+setting
 
 
 @lisp
 @lisp
 (setq org-todo-keywords
 (setq org-todo-keywords
   '((sequence "TODO(t)" "WAIT(w@@/!)" "|" "DONE(d!)" "CANCELED(c@@)")))
   '((sequence "TODO(t)" "WAIT(w@@/!)" "|" "DONE(d!)" "CANCELED(c@@)")))
 @end lisp
 @end lisp
 
 
+To record a timestamp without a note for TODO keywords configured with
+@samp{@@}, just type @kbd{C-c C-c} to enter a blank note when prompted.
+
 @noindent
 @noindent
 @vindex org-log-done
 @vindex org-log-done
 you not only define global TODO keywords and fast access keys, but also
 you not only define global TODO keywords and fast access keys, but also