From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Recurring tasks and arbitrary properties
Date: Sun, 22 Jan 2017 14:56:25 +0100 [thread overview]
Message-ID: <871svvfbau.fsf@luisa.c0t0d0s0.de> (raw)
In-Reply-To: <878tq3b4ht.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 22 Jan 2017 14:37:02 +0100")
Hello,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Michael Welle <mwe012008@gmx.net> writes:
>
>> I want to 'hide' the value of the SCHEDULED property and later restore
>> it. I can use inactive time stamps. But that means that I have to change
>> the value when deactivating the task and again, later when I activate
>> the task again. But it would have been nicer without doing so ;).
>
> It depends on what means "later". If it means "right after doing
> something to the headline", you could also store the actual time stamp
> in the lexical closure of a call-back function, without using a property
> drawer.
>
> There is `org-toggle-timestamp-type', too. We could extend it to process
> time stamp strings.
later means a lot later ;). Maybe months or even years. My personal use
case is, that I have dozens of recurring tasks. Now I leave the country
for a few months. The tasks only make sense, when I am here. So I want to
disable them and enable them, when I'm back. I can't use
org-cancel-repeater, because that loses the repeater.
There was a question on the ml about disabling recurring tasks many
moons ago. I will incorporate my new knowledge about properties into my
functions and then reply to that question.
Regards
hmw
next prev parent reply other threads:[~2017-01-22 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 19:06 Recurring tasks and arbitrary properties Michael Welle
2017-01-22 13:09 ` Nicolas Goaziou
2017-01-22 13:17 ` Michael Welle
2017-01-22 13:20 ` Nicolas Goaziou
2017-01-22 13:27 ` Michael Welle
2017-01-22 13:37 ` Nicolas Goaziou
2017-01-22 13:56 ` Michael Welle [this message]
2017-01-22 14:01 ` Nicolas Goaziou
2017-01-22 14:08 ` Michael Welle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871svvfbau.fsf@luisa.c0t0d0s0.de \
--to=mwe012008@gmx.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.