From: Robert Goldman <rpgoldman@sift.info>
To: emacs-orgmode@gnu.org
Subject: Notes on documentation
Date: Sat, 11 Oct 2008 16:04:49 -0500 [thread overview]
Message-ID: <48F114F1.1000400@sift.info> (raw)
I was reading over the agenda documentation in my current version of org
(6.08c) and noted a couple of things:
1. (nit): in the discussion of finding stuck projects:
"Lets[sic -- Let's] further"
2. In "The weekly/daily agenda":
" (1) For backward compatibility, the universal prefix `C-u' causes
all TODO entries to be listed before the agenda. This feature is
deprecated, use the dedicated TODO list, or a block agenda instead."
Would it be possible to expand this a little? In particular:
a. I use this because I like to have the todo list with my weekly
agenda, so that I can pick todo items to schedule in context. I guess I
don't off-hand see how having a view that only has the todo items would
replace this now-deprecated usage pattern.
b. Reading this, I didn't know what a "block agenda" was. Would it be
possible to add a cross reference to the Block Agenda section at this
point so that ignorant readers like me could easily find out more about
block agendas? I know that one need only look to the table of contents
to find this page, but when reading hypertext documentation one often
drills in deep and doesn't have a good sense of context. And it would
be an easy addition to make. [Indeed, the block agenda is exactly what
I should be using...]
I apologize if these have already been fixed in the current git version...
next reply other threads:[~2008-10-12 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 21:04 Robert Goldman [this message]
2008-10-12 6:30 ` Notes on documentation Carsten Dominik
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=48F114F1.1000400@sift.info \
--to=rpgoldman@sift.info \
--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).