From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Engster Subject: Re: Sorting TODOs with time-up Date: Mon, 30 Mar 2009 23:03:29 +0200 Message-ID: <87iqlqzpsu.fsf@arcor.de> References: <0FCA0437-9513-4C9F-BBFC-6B51A5E8E704@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LoOeA-0008Tp-Ij for emacs-orgmode@gnu.org; Mon, 30 Mar 2009 17:03:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LoOe7-0008SP-0k for emacs-orgmode@gnu.org; Mon, 30 Mar 2009 17:03:54 -0400 Received: from [199.232.76.173] (port=50792 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LoOe6-0008SI-Od for emacs-orgmode@gnu.org; Mon, 30 Mar 2009 17:03:50 -0400 Received: from main.gmane.org ([80.91.229.2]:37290 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LoOe6-0006AZ-1X for emacs-orgmode@gnu.org; Mon, 30 Mar 2009 17:03:50 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LoOe2-0006oo-8T for emacs-orgmode@gnu.org; Mon, 30 Mar 2009 21:03:46 +0000 Received: from dslc-082-082-160-168.pools.arcor-ip.net ([82.82.160.168]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Mar 2009 21:03:46 +0000 Received: from deng by dslc-082-082-160-168.pools.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Mar 2009 21:03:46 +0000 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 Carsten Dominik writes: > On Mar 30, 2009, at 4:46 PM, David Engster wrote: >> Thanks for the clarification. This is a bit confusing, since sorting >> by priority works in the todo list, but sorting with date does >> not. Also, since I call the function 'org-agenda', it is a bit >> unexpected that when I press 't' afterwards I don't really get an >> agenda but a TODO list, which seems to behave differently in some >> aspects from the normal agenda view I get when pressing 'a'. > > Yes, this is bad terminology, which evolved historically. > > "org-agenda" is a dispatcher for the different views that we call > "agenda views". > > One of the "agenda views" is the global todo list (on `t'), another > one is the "daily/weekly agenda" (on `'a), which is a list of what is > due today or this week. > I always try to call it explicitly > "daily/weekly agenda" to avoid some of that confusion, but I agree, if > I'd get a chance to start again I would use better terms. Now these > are so engrained in our mailing list culture and into tutorials etc > that I do not dare to change them anymore. Thank you for the explanation. Maybe this situation could be cleared up a bit in the manual. While browsing through chapter 10, I got the impression that the different views are just different filters, but that I'm always dealing with the same agenda mode, where each entry carries the same information. Maybe one could explicitly mention which commands and sorting strategies only apply to the daily/weekly agenda? I'd also say that the doc-string of org-agenda-sorting-strategy does not make this point clear enough. > Yes can use the text property on a, `org-hd-marker', which is a marker > pointing to the original location of the item. You can make your > function go back to get this information. > > For example with > (org-entry-get (get-text-property 0 'org-hd-marker a) "SCHEDULED") I will try that. Thank you for your help! -David