From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Goldman Subject: Notes on documentation Date: Sat, 11 Oct 2008 16:04:49 -0500 Message-ID: <48F114F1.1000400@sift.info> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KorPb-0008SP-Jb for emacs-orgmode@gnu.org; Sat, 11 Oct 2008 23:14:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KorPY-0008S6-Mh for emacs-orgmode@gnu.org; Sat, 11 Oct 2008 23:14:30 -0400 Received: from [199.232.76.173] (port=38737 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KorPY-0008S2-Ih for emacs-orgmode@gnu.org; Sat, 11 Oct 2008 23:14:28 -0400 Received: from outbound-mail-157.bluehost.com ([67.222.39.37]:55353) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1KorPY-0006bW-Em for emacs-orgmode@gnu.org; Sat, 11 Oct 2008 23:14:28 -0400 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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...