From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id iInrG4JSEWfCogAAe85BDQ:P1 (envelope-from ) for ; Thu, 17 Oct 2024 18:08:02 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id iInrG4JSEWfCogAAe85BDQ (envelope-from ) for ; Thu, 17 Oct 2024 20:08:02 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=M9+Ogtr6; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1729188482; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=AggFD31JbIpXv5Ode6tZ2n+IY1XHLxwqvdhWLHg+FPU=; b=TJJ9Jy94VwQF6KHY1zjo26R3vP2x2Ozpr0ZBQii8yrCP82MoDnQDhof4NvYH829w3+W4mH ptwys2Bf41iUmKFlhS+n5zGc6jabjqxPjArY3F8yIOMHWLWx8aZS6U453B0UPdu8Il69AD 0vOqJFoh6umIYc0/5SDprPLFP6jy5T3izALCTkYYMxqEqD22WjJM0shuVqhkoeyCRAi9Uf RvtuHK5hTuq+ohAob/3E8sIZs5/XqPwPpvSznBhP2oulJ+68iqq7Wgu4hZztVxaXPeWzwC qCYN1HyMp78ZckSznE07dGicFVY12hL4QEGcN/2dTJ/6DihZXtks9aYYqRPSOg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=M9+Ogtr6; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1729188482; a=rsa-sha256; cv=none; b=r3F/aVtHjK1k0JroJhvRYFlpb5MCIg9Oplt5IDn05OgAdzEThksYglc9WRZQV6TY+PDTdk 9zyskt3D8F3s/7ggIjZiA2QcBWsZCj6zM4h03J3e41ItCNosgEHPbmkVN6KvWjUWJVg312 2SNuARncfBZN05m4s5rfz2zIiqVHsAkMiVaAVG42k9t0auDIJGGq6oUDnARgCgFkCvBMuL 4drt+zFn7zuVPW8LKTwHp2BTeSOLoKL/gAAUfo9dBZvprvkerDz29BCzKEELlj5vqFrxtW r7eiIEnYvBy3YCo1SJQpSzHOBOGQNwuXjMasKCESHn7fGJRxZ8CGSBp7gZvlxg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 18B2F8E4E3 for ; Thu, 17 Oct 2024 20:08:01 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t1Utv-0005lw-Ga; Thu, 17 Oct 2024 14:07:07 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t1Utr-0005lV-JS for emacs-orgmode@gnu.org; Thu, 17 Oct 2024 14:07:04 -0400 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t1Uto-0005RK-Oq for emacs-orgmode@gnu.org; Thu, 17 Oct 2024 14:07:03 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 6AE35240027 for ; Thu, 17 Oct 2024 20:06:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1729188417; bh=1vEjtBtKGLmf76G5EtMqj6mANSWBUc6KTjCDx88YcXA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=M9+Ogtr6pYTWJdgKvaLUuVN9Hz2A6qNW7xDEZM5sLqRgFz8o0zk0uQdBKXWxWmVTF 0jYt/8xQb1r8Y1tFSeLZ641vd/iWPUcIKzhjiJt4CIu5/VpFqDCRp+dylcmuusu3mk kM68Bj4MzzpMnSSuAGRCqMe4rLZH/X6F+f3U4lCp9yEjPi0bMlmjd5yv3nwq+4dNqn pyXR3af9NfbBW20eBYTWzmayE+3XFTX1FAdIredMUWNmYeewdR7A9RPbHJ5MWywKMH 0TAZbwiPIMuKekzHqeuCr4HA241lW0RNqzUHjTL7jrQSLm/LE7Xt3o53TcXAUBaNNo vKLy4v8ZGG52w== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4XTwlN66L1z9rxD; Thu, 17 Oct 2024 20:06:56 +0200 (CEST) From: Ihor Radchenko To: Starlit Sky Cc: emacs-orgmode@gnu.org Subject: Re: [HELP] How to have a repeating task that begins at 06:50 and ++1h until 20:50, and then when DONE the last repeater for that day, it would ++1d at 06:50? In-Reply-To: <87o745dhnu.fsf@gmx.se> References: <87o745dhnu.fsf@gmx.se> Date: Thu, 17 Oct 2024 18:08:44 +0000 Message-ID: <871q0ezjo3.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx11.migadu.com X-Migadu-Spam-Score: -0.20 X-Spam-Score: -0.20 X-Migadu-Queue-Id: 18B2F8E4E3 X-TUID: nylW3Pvtg7JY Starlit Sky writes: > EXPECTED BEHAVIOR > > I want to have a repeating task that begins at 06:50 and ++1h until > 20:50, and then when DONE the last repeater for that day (20:50), it woul= d ++1d at 06:50 and ++1h until 20:50, and so on. I've tried many things, bu= t nothing seems to work. What you want is not how repeaters work in Org mode. In Org mode, each repeater is simply applied independently of others, which is exactly what you observe. No more complex behavior is current available out of the box. > SCHEDULED: <2024-09-29 Sun 06:50 ++1h ++1d>--<2024-09-29 Sun 20:50 ++1d> > ``` > ... ... and this is simply ambiguous Org mode syntax. As an implementation detail, Org mode will use the first repeater present in each timestamp. The second repeater in the first part of the timestamp is ignored. > Is there something I'm doing wrong with timing syntax, or do I really nee= d to do the following instead? > >> An alternative to using a repeater is to create a number of copies of a = task subtree, with dates shifted in each copy. The command =E2=80=98C-c C-= x c=E2=80=99 was created for this purpose; it is described in *note Structu= re Editing. As an alternative, you can try using `org-todo-repeat-hook' that is evaluated after all the timestamps with repeaters in a heading are updated. You can manually go through them again, applying custom repeater logic written by yourself, in Elisp. See `org-auto-repeat-maybe' code as an example what you need to do to update the repeaters from Elisp. --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at