|
|
@@ -1015,6 +1015,12 @@ If you would like to have a special ARCHIVE location for a single entry
|
|
|
or a (sub)tree, give the entry an @code{:ARCHIVE:} property with the
|
|
|
location as the value (@pxref{Properties and columns}).
|
|
|
|
|
|
+When a subtree is moved, it receives a number of special properties that
|
|
|
+record context information like the file from where the entry came, it's
|
|
|
+outline path the archiving time etc. Configure the variable
|
|
|
+@code{org-archive-save-context-info} to adjust the amount of information
|
|
|
+added.
|
|
|
+
|
|
|
@node Sparse trees, Plain lists, Archiving, Document structure
|
|
|
@section Sparse trees
|
|
|
@cindex sparse trees
|
|
|
@@ -2735,10 +2741,12 @@ With this setup, the command @kbd{C-c C-t} will cycle an entry from TODO
|
|
|
to FEEDBACK, then to VERIFY, and finally to DONE and DELEGATED. You may
|
|
|
also use a prefix argument to quickly select a specific state. For
|
|
|
example @kbd{C-3 C-c C-t} will change the state immediately to VERIFY.
|
|
|
-If you define many keywords, you can use in-buffer completion (see
|
|
|
-@ref{Completion}) to insert these words into the buffer. Changing a
|
|
|
-todo state can be logged with a timestamp, see @ref{Tracking TODO state
|
|
|
-changes} for more information.
|
|
|
+Or you can use @kbd{S-left} to go backward through the sequence. If you
|
|
|
+define many keywords, you can use in-buffer completion
|
|
|
+(@pref{Completion}) or even a special one-key selection scheme
|
|
|
+(@pxref{Fast access to TODO states}) to insert these words into the
|
|
|
+buffer. Changing a todo state can be logged with a timestamp, see
|
|
|
+@ref{Tracking TODO state changes} for more information.
|
|
|
|
|
|
@node TODO types, Multiple sets in one file, Workflow states, TODO extensions
|
|
|
@subsection TODO keywords as types
|
|
|
@@ -2902,6 +2910,10 @@ special faces for some of them. This can be done using the variable
|
|
|
("CANCELED" . (:foreground "blue" :weight bold))))
|
|
|
@end lisp
|
|
|
|
|
|
+While using a list with face properties as shown for CANCELED
|
|
|
+@emph{should} work, this does not aways seem to be the case. If
|
|
|
+necessary, define a special face and use that.
|
|
|
+
|
|
|
@page
|
|
|
@node Progress logging, Priorities, TODO extensions, TODO items
|
|
|
@section Progress Logging
|
|
|
@@ -2965,7 +2977,7 @@ after each keyword. For example, with the setting
|
|
|
|
|
|
@lisp
|
|
|
(setq org-todo-keywords
|
|
|
- '((sequence "TODO(t)" "WAIT(w@@/!)" "|" "DONE(d!)" "CANCELED(c@@)")))
|
|
|
+ '((sequence "TODO(t)" "WAIT(w@@/!)" "|" "DONE(d!)" "CANCELED(c@@)")))
|
|
|
@end lisp
|
|
|
|
|
|
@noindent
|
|
|
@@ -2977,12 +2989,13 @@ However, it will never prompt for two notes - if you have configured
|
|
|
both, the state change recording note will take precedence and cancel
|
|
|
the @samp{Closing Note}.}, and that a special note is recorded when
|
|
|
switching to WAIT or CANCELED. The setting for WAIT is even more
|
|
|
-special: The @samp{!} after the slash means that a time stamp should be
|
|
|
-recorded when @i{leaving} the WAIT state. This allows you to get a
|
|
|
-record when switching from WAIT back to TODO, without getting one when
|
|
|
-first turning an entry into a TODO.
|
|
|
+special: The @samp{!} after the slash means that in addition to the note
|
|
|
+taken when entering the state, a time stamp should be recorded when
|
|
|
+@i{leaving} the WAIT state. This allows you to get a record when
|
|
|
+switching from WAIT back to TODO, without getting one when first turning
|
|
|
+an entry into a TODO.
|
|
|
|
|
|
-You can use the exact same syntax for setting logging preferencs local
|
|
|
+You can use the exact same syntax for setting logging preferences local
|
|
|
to a buffer:
|
|
|
@example
|
|
|
#+SEQ_TODO: TODO(t) WAIT(w@@/!) | DONE(d!) CANCELED(c@@)
|
Carsten Dominik