From: Memnon Anon <firstname.lastname@example.org>
Subject: Re: suggestion for org manual
Date: Thu, 6 Sep 2012 16:27:40 +0000 (UTC) [thread overview]
Message-ID: <email@example.com> (raw)
Jonas Stein <firstname.lastname@example.org> writes:
> It says
> # You have enabled the habits module by customizing the variable
> I would expect here a link about customizing the variable org-modules,
> and how the setting looks like.
Well, customizing variables belongs to the emacs realm; given that, the
documentation is pretty good. One way to improve it could be something
like "You have enabled the habits module by "`M-x customize-variable'
org-modules". The customize buffer is fairly self-explanatory then I
guess. However, while this would make the manual more newcomer friendly,
it would also be less pleasant to read imho. ...
> It says
> # You must also have state logging for the 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.
> I would expect here
> # In order to get meaningful consistency graphs state logging for
> state "DONE" must be enabled.
> (Link to article about enable logging or explain it here.)
Tracking TODO state changes is in 5.3.2, i.e. just one "[" keypress
away, if you read the emacs info pages?! But a link rarely hurts, I
Thanks for your suggestions!
next prev parent reply other threads:[~2012-09-06 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 21:23 Jonas Stein
2012-09-06 16:27 ` Memnon Anon [this message]
2012-09-14 7:01 ` Bastien
2012-09-28 10:09 ` [PATCH] org.texi: New link (was: suggestion for org manual) Memnon Anon
2012-09-28 13:52 ` [PATCH] org.texi: New link Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).