On 2014-10-29 15:34, Robert Horn writes:
> Jay Iyer writes:
>
>> 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.
>
> It's most definitely useful. I'm not sure what you th
Jay Iyer writes:
> 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.
It's most definitely useful. I'm not sure what you think would be
"better". I make extensive use of dat
Thorsten Jolitz writes:
>* Jay Iyer 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-0
Am Wed, 29 Oct 2014 08:20:47 -0400
schrieb Nick Dokos :
> Detlef Steuer writes:
>
> > Hi Nick!
> >
> >
> >> 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.
> >>
> >
On 2014-10-29 03:59 Nick Dokos wrote:
> 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.
I would argue that datetress lend themselves fairly well for browsing
any kind of chro
Detlef Steuer writes:
> Hi Nick!
>
>
>> 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.
>>
>
>
> Oh, NO, don´t do that! Datetrees were a major enhancement for my
> workfl
Hi Nick!
> 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.
>
Oh, NO, don´t do that! Datetrees were a major enhancement for my
workflow. I use one as a kind of "lab logbo
Thorsten Jolitz writes:
> Jay Iyer 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
>
Jay Iyer 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
> Genera
Jay Iyer writes:
Hi Jay,
> 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
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
Jay Iyer 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 entr
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
13 matches
Mail list logo
