From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] org.texi: New link (was: suggestion for org manual)
Date: Fri, 28 Sep 2012 10:09:53 +0000 (UTC) [thread overview]
Message-ID: <874nmifp4a.fsf@mean.albasani.net> (raw)
In-Reply-To: 878vcd3x6b.fsf@altern.org
[-- Attachment #1: Type: text/plain, Size: 82 bytes --]
Bastien <bzg@altern.org> writes:
> Can you create a patch for this?
Like this?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Patch: Add link --]
[-- Type: text/x-diff, Size: 1349 bytes --]
From 365f6f3d23926647ce40979ca59f88f96086b713 Mon Sep 17 00:00:00 2001
From: Memnon Anon <gegendosenfleisch@gmail.com>
Subject: [PATCH] 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
---
doc/org.texi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index bb248a8..4b8a826 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -4273,10 +4273,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
--
1.7.10.4
next prev parent reply other threads:[~2012-09-28 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 21:23 suggestion for org manual Jonas Stein
2012-09-06 16:27 ` Memnon Anon
2012-09-14 7:01 ` Bastien
2012-09-28 10:09 ` Memnon Anon [this message]
2012-09-28 13:52 ` [PATCH] org.texi: New link Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874nmifp4a.fsf@mean.albasani.net \
--to=gegendosenfleisch@googlemail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).