From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Welle Subject: Re: Recurring tasks and arbitrary properties Date: Sun, 22 Jan 2017 14:56:25 +0100 Message-ID: <871svvfbau.fsf@luisa.c0t0d0s0.de> References: <87wpdo6xmr.fsf@luisa.c0t0d0s0.de> <87tw8rb5rg.fsf@nicolasgoaziou.fr> <87shobfd39.fsf@luisa.c0t0d0s0.de> <87h94rb59x.fsf@nicolasgoaziou.fr> <87inp7fcmk.fsf@luisa.c0t0d0s0.de> <878tq3b4ht.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56905) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cVIdH-0007us-Iz for emacs-orgmode@gnu.org; Sun, 22 Jan 2017 08:56:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cVIdE-0005Sp-Gy for emacs-orgmode@gnu.org; Sun, 22 Jan 2017 08:56:35 -0500 Received: from mout.gmx.net ([212.227.17.20]:58960) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cVIdE-0005SP-6T for emacs-orgmode@gnu.org; Sun, 22 Jan 2017 08:56:32 -0500 Received: from stella.c0t0d0s0.de ([89.15.236.235]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M4B71-1cESMv0Aq3-00rlrz for ; Sun, 22 Jan 2017 14:56:30 +0100 Received: from Stella (stella.c0t0d0s0.de [192.168.42.1]) by stella.c0t0d0s0.de (Postfix) with ESMTP id 6306EC45FC for ; Sun, 22 Jan 2017 14:56:25 +0100 (CET) In-Reply-To: <878tq3b4ht.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 22 Jan 2017 14:37:02 +0100") 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: emacs-orgmode@gnu.org Hello, Nicolas Goaziou writes: > Michael Welle 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