From: "Raimund Kohl-Füchsle" <rk-f@posteo.de>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inserting todo time range
Date: Thu, 27 Jun 2019 06:19:57 +0200 [thread overview]
Message-ID: <79b438da-01b5-4195-8800-2de231a00188@posteo.de> (raw)
In-Reply-To: <87y31odkmn.fsf@kyleam.com>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
Yepp, that is how I do it, too. I just thought there were something more convenient.
Thank you anyway :-)
Gesendet mit Blue
Am 27. Juni 2019, 00:53, um 00:53, Kyle Meyer <kyle@kyleam.com> schrieb:
>Raimund Kohl-Füchsle <rk-f@posteo.de> writes:
>
>> I do have a recurring task Mo-Fri, but not at weekends.
>>
>> I searched the manual and it offers a time range - like
>>
>> ** Test Time range
>>
>> <2004-08-23 Mon>--<2004-08-26 Thu>
>>
>> But, of course, this doesn't mark a recurring task.
>>
>> 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 done, too.
>>
>> So how 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 heading for each day of interest. So, in your case, something like
>
> ** TODO task (Mon)
> SCHEDULED: <2019-07-01 Mon ++1w>
>
> ** TODO task (Tue)
> SCHEDULED: <2019-07-02 Tue ++1w>
>
> [...]
>
> ** TODO task (Fri)
> SCHEDULED: <2019-07-05 Fri ++1w>
>
>--
>Kyle
[-- Attachment #2: Type: text/html, Size: 1977 bytes --]
next prev parent reply other threads:[~2019-06-27 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 19:16 Inserting todo time range Raimund Kohl-Füchsle
2019-06-26 22:53 ` Kyle Meyer
2019-06-27 4:19 ` Raimund Kohl-Füchsle [this message]
2019-06-27 6:48 ` Michael Welle
2019-06-30 0:13 ` Spenser Truex
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=79b438da-01b5-4195-8800-2de231a00188@posteo.de \
--to=rk-f@posteo.de \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
/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).