From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Raimund_Kohl-F=FCchsle?= Subject: Re: Inserting todo time range Date: Thu, 27 Jun 2019 06:19:57 +0200 Message-ID: <79b438da-01b5-4195-8800-2de231a00188@posteo.de> References: <87y31odkmn.fsf@kyleam.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----80IXSF9XGDLYT5L788YJKVH7PMVUHJ" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46972) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgLtD-0005c0-8t for emacs-orgmode@gnu.org; Thu, 27 Jun 2019 00:20:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hgLtB-0003BX-LW for emacs-orgmode@gnu.org; Thu, 27 Jun 2019 00:20:02 -0400 Received: from mout02.posteo.de ([185.67.36.66]:37521) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hgLtB-00038e-3a for emacs-orgmode@gnu.org; Thu, 27 Jun 2019 00:20:01 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 4A0892400E5 for ; Thu, 27 Jun 2019 06:19:59 +0200 (CEST) In-Reply-To: <87y31odkmn.fsf@kyleam.com> 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" To: Kyle Meyer Cc: emacs-orgmode@gnu.org ------80IXSF9XGDLYT5L788YJKVH7PMVUHJ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Yepp, that is how I do it, too=2E I just thought there were something more = convenient=2E Thank you anyway :-) =E2=81=A3Gesendet mit Blue =E2=80=8B = Am 27=2E Juni 2019, 00:53, um 00:53, Kyle Meyer schrie= b: >Raimund Kohl-F=C3=BCchsle writes: > >> I do have a r= ecurring task Mo-Fri, but not at weekends=2E >> >> I searched the manual an= d it offers a time range - like >> >> ** Test Time range >> >> =C2= =A0=C2=A0=C2=A0 <2004-08-23 Mon>--<2004-08-26 Thu> >> >> But, of course, th= is doesn't mark a recurring task=2E >> >> If instead I would use >> >> = ** TODO Test Time range >> >> =C2=A0=C2=A0=C2=A0 <2004-08-23 Mon>--<20= 04-08-26 Thu> >> >> then this for org-mode would just be one todo; if I mar= k it done on >Mon >> all other days are marked as done, too=2E >> >> So ho= w would I schedule a daily TODO only, say, this week from Mo - >Fr? > >The = way I handle this, which isn't particularly elegant, is to just >have >a he= ading for each day of interest=2E So, in your case, something like > > **= TODO task (Mon) > SCHEDULED: <2019-07-01 Mon ++1w> > > ** TODO task (T= ue) > SCHEDULED: <2019-07-02 Tue ++1w> > > [=2E=2E=2E] > > ** TODO tas= k (Fri) > SCHEDULED: <2019-07-05 Fri ++1w> > >-- >Kyle ------80IXSF9XGDLYT5L788YJKVH7PMVUHJ Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Yepp, that is how I do it, too= =2E I just thought there were something more convenient=2E

Thank you anyway :-)

Gesendet mit Blue
Am 27=2E Juni 2019, um 00:53, Kyle Meyer <kyle@kyleam=2Ecom> schrieb:
Raimund Kohl-F=C3=BCchsle <rk-f@posteo=2Ede> writes:

I do have a recurring task Mo-Fr= i, but not at weekends=2E

I searched the manual and it offers a tim= e range - like

** Test Time range

  &nbs= p; <2004-08-23 Mon>--<2004-08-26 Thu>

But, of course, t= his doesn't mark a recurring task=2E

If instead I would use

= ** TODO Test Time range

    <2004-08-23= Mon>--<2004-08-26 Thu>

then this for org-mode would just = be one todo; if I mark it done on Mon
all other days are marked as don= e, too=2E

So how would I schedule a daily TODO only, say, this week= from Mo - Fr?

The way I handle this, which isn't parti= cularly elegant, is to just have
a heading for each day of interest=2E = So, in your case, something like

** TODO task (Mon)
SCHEDULED= : <2019-07-01 Mon ++1w>

** TODO task (Tue)
SCHEDULED:= <2019-07-02 Tue ++1w>

[=2E=2E=2E]

** TODO task (= Fri)
SCHEDULED: <2019-07-05 Fri ++1w>
------80IXSF9XGDLYT5L788YJKVH7PMVUHJ--