From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Baker Subject: "constellations" Re: relative deadlines Date: Thu, 11 Dec 2014 19:48:00 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1137d89ed7208a0509fa3f65 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57301) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XzEPC-0004T4-RG for emacs-orgmode@gnu.org; Thu, 11 Dec 2014 19:48:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XzEP8-0005an-U3 for emacs-orgmode@gnu.org; Thu, 11 Dec 2014 19:48:26 -0500 Received: from mail-ob0-x22f.google.com ([2607:f8b0:4003:c01::22f]:36387) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XzEP8-0005Zd-Je for emacs-orgmode@gnu.org; Thu, 11 Dec 2014 19:48:22 -0500 Received: by mail-ob0-f175.google.com with SMTP id wp4so5881093obc.6 for ; Thu, 11 Dec 2014 16:48:21 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --001a1137d89ed7208a0509fa3f65 Content-Type: text/plain; charset=UTF-8 Date: Tue, 09 Dec 2014 12:05:39 -0500 From: dboyd2@mmm.com (J. David Boyd) To: emacs-orgmode@gnu.org Subject: Re: [O] relative deadlines J. David Boyd < dboyd2@mmm.com > wrote on Dec 9: > Jeffrey Brent McBeth writes: > > From time to time (each time I delve into using org-mode for deadlines > > before my habits fall apart), I find the desire to have some form of > > relative deadlines. By this I mean, that there are often sequences of > > tasks that I know the time required to complete and when things are > > due. These tasks may repeat (usually do). > > > > It would be awful helpful to me, but I would guess few others, as a > > search didn't find much, for there to be some annotation like this > > (example is farcical, notation is notional) > > > > * Go on date > > DEADLINE: <2014-12-25> > > ** Ask Girl #<-3w># > > ** Wash Hair #<-2w># > > ** Make Money #<-1w2d># > > ** Get in Car #<-0d># > > ** Call her back #<+1w># > > > > that in the agenda view would show as a sequence of tasks with the following dates > > Go on date <2014-12-25> > > Ask Girl <2014-12-04> > > Wash Hair <2014-12-11> > > Make Money <2014-12-16> > > Get in Car <2014-12-25> > > Call her back <2015-01-01> > > > > I have a python function that can take a stripped down org file and > > places an active date after each ## (or inactive after > > #[block]#), that I hacked up today to see if it would really be as > > useful as I thought, but I keep thinking that someone somewhere must > > have scratched this itch elsewhere, and having to partially parse org > > in python and modify the text rather than having my agenda smart > > enough to figure it out gives me pause... > > > > If nobody have better ideas, are the block delimiters I'm using going > > to conflict with some other feature in org that I'm just not using > > yet? > > > > The main functuionality I'm stumbling toward is having an easily > > moveable end date (so replacing the block with absolute dates is a > > nono). > > > > Thanks for your attention, > > Jeffrey McBeth *> > I think like that as well. I know when some _thing_ has to be done. Then I > start thinking of all the support items in relative terms to the main one. > > You should add this to org mode, if able. It would be a nice addition... > > Dave* The relative deadline part should be implemented, I agree. I also like the collection of intermediate tasks. Does Emacs have a name for that? Because I used to call that a "constellation" of deadlines, and if we have the relative timestamps, the constellation would be easy to implement on the fly. This addresses Jeffrey's original intention, you see, if I explain. If I have an appointment at 4pm and I know it is a 40m drive AND I may need to get dressed formally (that takes 30m), then I really can't tell the Org system "Notify me at 4pm". Instead, I *need* to have it say, "Get me driving by 320pm, and if I need to dress up, then get that started by 250pm". Really, for me, the "appointment at 4" starts much earlier. Also, keep track of the fact that I will probably come right back, so if the appointment ends at 530, then I won't get back until 610pm. Now if Jeffrey wants to schedule something like this BUT needs to take into account that he already has a 6pm appointment, then his request for an "easily movable" end is reasonable. When he is setting up the appointment, Org needs to tell him, as soon as possible, that there is a conflict, and so when they suggest "330pm instead of 4pm?" he can try that. Tom --001a1137d89ed7208a0509fa3f65 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Date: Tue, 09 Dec 2014 12:05:39 -= 0500
From: dboyd2@mmm.com (J. David Boyd)<= br> To: emacs-orgmode@gnu.org
Subject: Re: [O] relative deadlines

J. David Boyd < dboyd2@mmm.com >= ; wrote on Dec 9:
> Jeffrey Brent McBeth <mcbeth@broggs.org> writes:
>=20 > From time to time (each time I delve into using org-mode for deadlines=
> > before my habits fall apart), I find the desire to have some form= of
> > relative deadlines.=C2=A0 By this I mean, that there are often se= quences of
> > tasks that I know the time required to complete and when things a= re
> > due.=C2=A0 These tasks may repeat (usually do).
> >
> > It would be awful helpful to me, but I would guess few others, as= a
> > search didn't find much, for there to be some annotation like= this
> > (example is farcical, notation is notional)
>=20 >
> > * Go on date
> >=C2=A0 DEADLINE: <2014-12-25>
> >=C2=A0 ** Ask Girl #<-3w>#
> >=C2=A0 ** Wash Hair #<-2w>#
> >=C2=A0 ** Make Money #<-1w2d>#
> >=C2=A0 ** Get in Car #<-0d>#
> >=C2=A0 ** Call her back #<+1w>#
> >
> > that in the agenda view would show as a sequence of tasks with the fo= llowing dates
> > Go on date <2= 014-12-25>
> > Ask Girl <2014-12-04>
> > Wash Hair <20= 14-12-11>
> > Make Money <2= 014-12-16>
> > Get in Car <2= 014-12-25>
> > Call her back <2015-01-01>
> >
> > I have a python function that can take a stripped down org file a= nd
> > places an active date after each #<block># (or inactive aft= er
> > #[block]#), that I hacked up today to see if it would really be a= s
> > useful as I thought, but I keep thinking that someone somewhere m= ust
> > have scratched this itch elsewhere, and having to partially parse= org
> > in python and modify the text rather than having my agenda smart<= br> > > enough to figure it out gives me pause...
> >
> > If nobody have better ideas, are the block delimiters I'm usi= ng going
> > to conflict with some other feature in org that I'm just not = using
> > yet?
> >
> > The main functuionality I'm stumbling toward is having an eas= ily
> > moveable end date (so replacing the block with absolute dates is = a
> > nono).
> >
> > Thanks for your attention,
> >=C2=A0 Jeffrey McBeth
>
> I think like that as well.=C2=A0 I know when some _thing_ has to be do= ne.=C2=A0 =C2=A0Then I
> start thinking of all the support items in relative terms to the main = one.
>
> You should add this to org mode, if able.=C2=A0 It would be a nice add= ition...
>
> Dave

The relative deadline part should be implemented= , I agree.

I also like the collection of intermediate tasks. D= oes Emacs have a name for that?=C2=A0 Because I used to call that a "c= onstellation" of deadlines, and if we have the relative timestamps, th= e constellation would be easy to implement on the fly.

This ad= dresses Jeffrey's original intention, you see, if I explain.=C2=A0 If I= have an appointment at 4pm and I know it is a 40m drive AND I may need to = get dressed formally (that takes 30m), then I really can't tell the Org= system "Notify me at 4pm".=C2=A0 Instead, I *need* to have it sa= y, "Get me driving by 320pm, and if I need to dress up, then get that = started by 250pm".=C2=A0 Really, for me, the "appointment at 4&qu= ot; starts much earlier.=C2=A0 Also, keep track of the fact that I will pro= bably come right back, so if the appointment ends at 530, then I won't = get back until 610pm.

Now if Jeffrey wants to schedule somethi= ng like this BUT needs to take into account that he already has a 6pm appoi= ntment, then his request for an "easily movable" end is reasonabl= e.=C2=A0 When he is setting up the appointment, Org needs to tell him, as s= oon as possible, that there is a conflict, and so when they suggest "3= 30pm instead of 4pm?" he can try that.


Tom
--001a1137d89ed7208a0509fa3f65--