From: Jay Iyer <jayiyer09@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to extract TODOs from date-tree
Date: Wed, 29 Oct 2014 08:28:45 -0700 [thread overview]
Message-ID: <CAGGEobUq7ew33f2-+bwBkr69wV6Y6A6ds2jg7JjUo6GFj_oefA@mail.gmail.com> (raw)
In-Reply-To: <CAGGEobVUHRBhpa0S7ojbhWkL=pAMDeqmrW+k0_gysbrh4A214g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4048 bytes --]
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 <jayiyer09@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 <jayiyer09@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
>>
>
>
[-- Attachment #2: Type: text/html, Size: 5960 bytes --]
next prev parent reply other threads:[~2014-10-29 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 15:53 How to extract TODOs from date-tree Jay Iyer
2014-10-28 16:20 ` Thorsten Jolitz
2014-10-28 16:54 ` Jay Iyer
2014-10-28 17:26 ` Thorsten Jolitz
2014-10-28 17:28 ` Thorsten Jolitz
2014-10-29 2:59 ` Nick Dokos
2014-10-29 8:24 ` Detlef Steuer
2014-10-29 12:20 ` Nick Dokos
2014-10-29 15:15 ` Detlef Steuer
2014-10-29 12:27 ` Alexander Baier
2014-10-29 15:28 ` Jay Iyer [this message]
2014-10-29 19:34 ` Robert Horn
2014-11-02 21:00 ` Alan Schmitt
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=CAGGEobUq7ew33f2-+bwBkr69wV6Y6A6ds2jg7JjUo6GFj_oefA@mail.gmail.com \
--to=jayiyer09@gmail.com \
--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).