From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id aJ7eEHR0OmQfMwAASxT56A (envelope-from ) for ; Sat, 15 Apr 2023 11:55:00 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id CKLmD3R0OmQ/wAAAG6o9tA (envelope-from ) for ; Sat, 15 Apr 2023 11:55:00 +0200 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 1049719BF0 for ; Sat, 15 Apr 2023 11:55:00 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pncbv-0004dZ-4V; Sat, 15 Apr 2023 05:54:23 -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 1pncbt-0004dK-NX for emacs-orgmode@gnu.org; Sat, 15 Apr 2023 05:54:21 -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 1pncbr-0000CK-KJ for emacs-orgmode@gnu.org; Sat, 15 Apr 2023 05:54:21 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 5A54F2401F0 for ; Sat, 15 Apr 2023 11:54:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1681552457; bh=L3ypWvXryZqHSSzFrYUehu/lgkKyGU5P5qP7lXPdBrA=; h=From:To:Cc:Subject:Date:From; b=aY1X8mjLzozMtY6QjjI+pbZSjaC/whutXoz0k8tNmPKmdPyZU6ffly0GYcAM9UJ1E 5XiRNZYdW//sbHXasieeH55o0+jglCoZQgwfYzlb0s+f8yfYzHfnCEVQgQtbTzg2Dc IKYsx7yG2HCDInzCYXRnRGJD0ZjzlLa19tQrxmCXhsY395zY/+lq5qBsTnVwCzxyk+ aCmC+hmeVidkVEaxgiZPMKdl8CccJlo1ZbtoUGZGKEh1w0VptBULFpeU9lV6OhqnUL OG37ayTYahia87KfRewFG9g4FzD6+kUlbFpJ+KtYvqft5IENU4JZj0JUctXU8t5jKF PlnH5iQ1yTUJw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Pz7vD5y89z6tvx; Sat, 15 Apr 2023 11:54:16 +0200 (CEST) From: Ihor Radchenko To: Jack Kamm Cc: emacs-orgmode@gnu.org, mail@nicolasgoaziou.fr Subject: Re: [RFC] ox-icalendar: Unscheduled tasks & repeating tasks In-Reply-To: <87wn2d4z3q.fsf@gmail.com> References: <874jq75okg.fsf@gmail.com> <87o7oetneo.fsf@localhost> <87fs92bdvf.fsf@gmail.com> <87o7nql2sq.fsf@localhost> <87wn2d4z3q.fsf@gmail.com> Date: Sat, 15 Apr 2023 09:56:54 +0000 Message-ID: <878retlb89.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain 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_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 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-Flow: FLOW_IN X-Migadu-Country: US ARC-Seal: i=1; s=key1; d=yhetil.org; t=1681552500; a=rsa-sha256; cv=none; b=A5tzOwX46Zfk6OwjKnfO0uBdap7zpYXiG4aksttI4amgJznu0JiNOQT9+auGw3LlQFqGqr 2IQpcHGbnMAbSmVWTvVAkiGW3tlIeexmLcFfiEGTzorbbWFBIcHE5MrFi20XTn4WIblUIK +HZTnPMloF04f+/DRyS7nUfKg9PV+yNd0To+X+ZqKotQUO6eDvlU1HZ1jfrCkPKAhqQgcg R6Aqnsu/kcKsREDiw/KQU4MJQgo3yclgV+rIfoTzC+sMqoFhUAAKE8bE6itdUM37iaXXA2 Pyu7yPiIF3ayDL2D8LGd4R89u3dUW0J6TIlJ2iEvYZi8d7dmGQXjilFdDpLaeg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=aY1X8mjL; 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=1681552500; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=dAV7eqARKQoBFJuGfJpUCmbcsEx0MwLxwrokqScMbUs=; b=I1iFDCLbdCxOSwIP6kR65yQEAO9ACU1iuamgcKYAXPyNz6LsvbYXEz/OkB/Tnw6QR1gJ0u gB8gxRYZhVuXNPFwTyN0JzJNgReOxmYYc6gwufMptg/zFZ6dxuZoaH2eILEGJpZfaxpUSi +7kgvIKWYTgQzQTVdfQdO3X3+gnb4awz+DfXwxTuxX5CBB7zdgq7eo7QqvyxQAVKrS72Ls Ag+yJnpozx9C0t0m+uZ2l0sFjgGLsmsOnm4JrCa/3FqwbZ+VshwM+OdqY1eMktogbmBwyM TIzZW6gZsg2HbRzbX5LV9h7m/yCHK476r6NjSxHV9fNASdb/ABjqU5p0yyGq6w== X-Migadu-Queue-Id: 1049719BF0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=aY1X8mjL; 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 X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -7.51 X-Spam-Score: -7.51 X-TUID: hLTuVkUt9030 Jack Kamm writes: > So the RRULE applies to both DTSTART and DUE, and the repeats continue > past DUE. > > But, another thing to note from the definition of DTSTART [2]: > > This property [DTSTART] is REQUIRED in all types of recurring > calendar components that specify the "RRULE" property. > > So technically, a standalone DEADLINE + repeater isn't allowed -- a > repeating task must always have a start date. May we then use org-deadline-warning-days/timestamp warntime spec as DTSTART? VALARM component is not fitting for warning days anyway. > But still, maybe we should stick to the requirement, and only export > repeater on SCHEDULED. That would simplify the implementation. The > downside is that repeating deadlines won't show up in iCalendar, which > seems undesirable. Agree. We should better stick to the spec. >> If we want to leave as many options as possible to the users, we can (1) >> Implement ICALENAR_DUE property that will set DUE explicitly on export; >> (2) ICALENDAR_DUE may allow special values that will indicate how to >> treat Org DEADLINEs - make them into DUE, use Org DEADLINE as a >> bound for SCHEDULED repeater, or ignore DEADLINE completely. > > A couple of these behaviors can already be achieved by customizing > `org-icalendar-use-deadline' (making DUE or ignoring). For using > DEADLINE as a bound, we could potentially add another option for that. Yup. That's what I meant. >> Is there any reason for this? May we instead export to a single VEVENT >> with appropriate RDATE list? > > I guess if there are multiple timestamps with repeaters, it's easier to > export these as separate VEVENT, because it's not possible to have > multiple RRULE in one VEVENT. > > But, your suggestion earlier in thread could also solve this: in case of > different repeaters, we can use RDATE to generate occurrences manually > sufficiently far into future (with defcustom for "how far"). RDATE is exactly what I had in mind here. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at