Thorsten Jolitz <address@hidden> writes: >* Jay Iyer <address@hidden> writes:* > >*> Hi Thorsten,* >*> The file entries are as follows and the task/note/project sub-heads * >*> generally don't have active/inactive timestamps except when a * >*> scheduling/deadline is specified. Thanks.* >*> ** 2014-10 October* >*> *** 2014-10-01 Wednesday* >*> **** TODO first task* >*> **** General note entry* >*> **** Project :prj:* > >* I just read the term 'datetree' again in another post, maybe I'm not* >* up-to-date and it is idiomatic Org-mode use, then sorry for the noise ...*
I don't think it's well documented (I couldn't find a reference in the manual) or well supported. org-capture does provide for it (see the doc for org-capture-templates) but afaict that's the only significant use of it - org-agend uses it for diary-related stuff and org-archive has to be able to archive it and that's it. The (rather thin) support for it is in org-datetree.el. If there are use cases out there, it might be worth collecting them and then thinking about how to support them better. If there aren't, maybe it should be thrown out. -- Nick I think removing support for date tree would be very disruptive, at least for me. Datetree is the fundamental structure of my Org files (I have two Org files: work and a personal journal) as I use capture templates for almost everything with the captured items filed neatly in the date trees and this structure provides a better sense of life flow for me. I rely on Agenda and sparse trees to extract the info/tasks/projects list. Please keep date tree intact. Thank you. -jay On Tue, Oct 28, 2014 at 9:54 AM, Jay Iyer <jayiye...@gmail.com> wrote: > Hi Thorsten, > > The file entries are as follows and the task/note/project sub-heads generally > don't have active/inactive timestamps except when a scheduling/deadline is > specified. Thanks. > > ** 2014-10 October > > *** 2014-10-01 Wednesday > > **** TODO first task > > **** General note entry > > **** Project :prj: > > > Jay Iyer <address@hidden> writes: > > Hi, > >* I have my Org files set up as date-trees containing a mix of notes,* > >* tasks and projects. I now have a need to generate a list of projects* > >* and tasks filed under specific date-tree or in a range of dates. Is it* > >* possible to get this listing from the date-trees if the entries* > >* themselves don't have date/time in timestamps or in properties* > >* settings? I couldn't find a solution in the archives. Please advise.* > >* Thank you.* > > what is a date tree? This: > > ,---- > | * <2014-10-28 Di> > `---- > > ? > > If the date-tree is the parent and has a timestamp, then the entries > are part of the contents of parent, and you can use this function to > map over the parents > > ,----[ C-h f org-element-map RET ] > | org-element-map is a compiled Lisp function in `org-element.el'. > | > | (org-element-map DATA TYPES FUN &optional INFO FIRST-MATCH > | NO-RECURSION WITH-AFFILIATED) > | > | Map a function on selected elements or objects. [...] > `---- > > and this to get their contents > > ,----[ C-h f org-element-contents RET ] > | org-element-contents is a compiled Lisp function in `org-element.el'. > | > | (org-element-contents ELEMENT) > | > | Extract contents from an ELEMENT. > `---- > > and then 'org-element-property' and 'org-element-put-property' to get > and set timestamp info from the parent and any other info from the child > entries. > > -- > cheers, > Thorsten > > > > On Tue, Oct 28, 2014 at 8:53 AM, Jay Iyer <jayiye...@gmail.com> wrote: > >> Hi, >> I have my Org files set up as date-trees containing a mix of notes, tasks >> and projects. I now have a need to generate a list of projects and tasks >> filed under specific date-tree or in a range of dates. Is it possible to >> get this listing from the date-trees if the entries themselves don't have >> date/time in timestamps or in properties settings? I couldn't find a >> solution in the archives. Please advise. >> Thank you. >> -jay >> > >
