diff options
| author | Memnon Anon <gegendosenfleisch@gmail.com> | 2012-09-28 15:51:56 +0200 |
|---|---|---|
| committer | Bastien Guerry <bzg@altern.org> | 2012-09-28 15:51:56 +0200 |
| commit | 213e2934c16d5e9034e0a8c6b7a77cbcd8afbcf6 (patch) | |
| tree | 1a051846d9026e5cd5d2451e68b1d6d9f1f870a8 | |
| parent | c173b19b05c0dc92913ad55981d1351c8d28c88a (diff) | |
| download | org-mode-213e2934c16d5e9034e0a8c6b7a77cbcd8afbcf6.tar.gz | |
Add a link to documentation
* doc/org.texi (Tracking your habits): Point to the
"Tracking TODO state changes" section.
As suggested by Jonas Stein.
TINYCHANGE
| -rw-r--r-- | doc/org.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/org.texi b/doc/org.texi index 082fe13..57ed1cf 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -4267,10 +4267,10 @@ The TODO may also have minimum and maximum ranges specified by using the syntax @samp{.+2d/3d}, which says that you want to do the task at least every three days, but at most every two days. @item -You must also have state logging for the @code{DONE} state enabled, in order -for historical data to be represented in the consistency graph. If it is not -enabled it is not an error, but the consistency graphs will be largely -meaningless. +You must also have state logging for the @code{DONE} state enabled +(@pxref{Tracking TODO state changes}), in order for historical data to be +represented in the consistency graph. If it is not enabled it is not an +error, but the consistency graphs will be largely meaningless. @end enumerate To give you an idea of what the above rules look like in action, here's an |