From: Tim Cross <theophilusx@gmail.com>
To: Cecil Westerhof <cldwesterhof@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Scheduling and calendar-day-of-week
Date: Sat, 07 Apr 2018 05:52:28 +1000 [thread overview]
Message-ID: <87po3cyuwz.fsf@gmail.com> (raw)
In-Reply-To: <CAG-LmmBs3pY5NXfckWP9juJLtmqxRb4BNfRU=KOD88P1t7n1dA@mail.gmail.com>
Cecil Westerhof <cldwesterhof@gmail.com> writes:
> There is something I want to do on Monday, Wednesday and Friday. So I tried:
> *** TODO Monday, Wednesday and Friday
> SCHEDULED: <%%(memq (calendar-day-of-week date) '(1 3 5))>
>
> This seems to work: I see the activity on the correct days.
> But then I changed today's entry to DONE. But then all are gone in my
> agenda view.
> What I want is for today's item to be 'gone' and the future ones still
> displayed as TODO. Is that possible?
Use of diary sexp entries is limited and this may not work. You may be
better off using org built in support for repeated scheduled/deadline
tasks.
The other thing to note is that you need to use a different command when
marking a repeating item as done. The manual has the following -
#+BEGIN_QUOTE
To mark a task with a repeater as ‘DONE’, use ‘C-- 1 C-c C-t’ (i.e.,
‘org-todo’ with a numeric prefix argument of -1.)
A timestamp(2) will be added under the deadline, to keep a record
that you actually acted on the previous instance of this deadline.
As a consequence of shifting the base date, this entry will no longer
be visible in the agenda when checking past dates, but all future
instances will be visible.
#+END_QUOTE
--
Tim Cross
prev parent reply other threads:[~2018-04-06 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 7:46 Scheduling and calendar-day-of-week Cecil Westerhof
2018-04-06 8:23 ` stardiviner
2018-04-06 14:16 ` Nick Dokos
2018-04-06 16:46 ` Brian Shine
2018-04-06 17:13 ` Brian Shine
2018-04-06 19:52 ` Tim Cross [this message]
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=87po3cyuwz.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=cldwesterhof@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).