From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: suggestion: options for chronological agenda Date: Sat, 26 Sep 2009 07:57:40 -0400 Message-ID: References: <4b11f87e0909252202m93e3659gbc6d9c37c35be174@mail.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 1MrVuP-0004Z1-AK for emacs-orgmode@gnu.org; Sat, 26 Sep 2009 07:57:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MrVuK-0004Yd-5H for emacs-orgmode@gnu.org; Sat, 26 Sep 2009 07:57:48 -0400 Received: from [199.232.76.173] (port=42134 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MrVuJ-0004Ya-VA for emacs-orgmode@gnu.org; Sat, 26 Sep 2009 07:57:44 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:54279) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MrVuJ-0002IE-KU for emacs-orgmode@gnu.org; Sat, 26 Sep 2009 07:57:43 -0400 In-Reply-To: <4b11f87e0909252202m93e3659gbc6d9c37c35be174@mail.gmail.com> (Ilya Shlyakhter's message of "Sat, 26 Sep 2009 01:02:52 -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: Ilya Shlyakhter Cc: emacs-orgmode Ilya Shlyakhter writes: > I often need to find recently modified entries. I try to timestamp > entries I work on with the active timestamps (in angular brackets), > and use the C-x a L command. This mostly works, but is imperfect: > - when i use time logging, it inserts "inactive" timestamps that > are not found this way. so, i can't use this to find "recently worked > on" entries. I believe that's because org-mode, in general, treats active timestamps as scheduling data -- i.e., things you need to do. I.e., it is optimized for using inactive timestamps to indicate "recently worked on" items. > - it looks at the _first_ timestamp in an entry, rather than the > _last_ timestamp Could you give an example? When I try C-c a L, it creates separate instances for each timestamp in an entry. E.g., the following file... --8<---------------cut here---------------start------------->8--- * A test <2009-09-25 Fri> <2009-09-26 Sat> --8<---------------cut here---------------end--------------->8--- becomes... --8<---------------cut here---------------start------------->8--- Friday 25 September 2009 A test ------------------------------------------------------------------------------- Saturday 26 September 2009 A test --8<---------------cut here---------------end--------------->8--- > - it is limited to one file . would be much better if it could > be made to work across the entire agenda. > - it would be fine to have the option to limit it to entries > within the last, say, week, if that would speed it up. Depending on whether or not Carsten decides to change the behavior of the timeline view ;) , you could always use a custom agenda command to accomplish the same thing. > > The suggestion is to enhance the timeline agenda with options to: > - recognize "inactive" timestamps ([in square brackets]) See the variable org-agenda-inactive-timestamps. > It would also be _really_ great if the chronological listing could be > filtered to contain only entries matching a certain tag/property > query. Try filtering the timeline with "/". Best, Matt