From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id ELW2OBkgeGYXJQEA62LTzQ:P1 (envelope-from ) for ; Sun, 23 Jun 2024 13:16:10 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id ELW2OBkgeGYXJQEA62LTzQ (envelope-from ) for ; Sun, 23 Jun 2024 15:16:10 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=oZbYSDXq; 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=1719148569; 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=4r+DeMAgn7tMHLJgxTS2R/0Tpv9Dt9S+ic2VV1ZWOng=; b=BZN9y0BhgXoeZoHWn6igfhkxCHN0KQbNMjHBxqeXgAac68vQ5s6Cw/JJS4yuaKFwJIUX1L xhnAMGjX9AYrUMzWw3DnbzszZKzvmGshJ+U40sOYoaNsAwmf2CZD/rPVlZxkUI9i9cC6je rSBmegUONVTssUgxH0dZosbLR+8AWREWEzwO+7kKXlI9Worykii2wc8/IqIMHbFbhntqEV AAGoyXxKZDF10HyfqNSCZX/b/zzp97ZV8UmsDZOObD44QSSU1igCexWB7au/vrEBZPO/VW ZarVFrJPKgfPjp5cu4JBl0Kxss5qz1YpCMcJk2GHhjTNrg6lsid23b78XhfWjQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=oZbYSDXq; 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=1719148569; a=rsa-sha256; cv=none; b=RVRBPxolLcbUrPfOSgPR3zehtUhd3wLwdVI4R4SM7Ad9o0ald7fhMJahY235uVYiaLqWgl zQ0J9N8fibVxCImNjuLEIG0e2xGseVcb0VlYNzEUit8G9yRrWE+KUhu4WFewMcszFMBgcc kbsODsLrApqwwZcYGD9OEU0jy6pX88kTTgMKozoAz2RjtiYukwQBbfgfiOkFicIC/U9C1h HjLodSaMMu0Svto3c+b+mGyVKPm3Gb8mYjR9+R/3kziZWN/rdyeRRHhsW+fw/q+5L76n9P KBMEkL/O2fVnXQlSkwVeUKWQSrYXa4n/G9iVzCU4HMRhES+EMCSQW7FYazShkw== 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 868833E1D9 for ; Sun, 23 Jun 2024 15:16:09 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sLN40-0006Lk-Bv; Sun, 23 Jun 2024 09:15:24 -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 1sLN3z-0006LV-3v for emacs-orgmode@gnu.org; Sun, 23 Jun 2024 09:15:23 -0400 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sLN3v-0001HB-PW for emacs-orgmode@gnu.org; Sun, 23 Jun 2024 09:15:22 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 0415E240103 for ; Sun, 23 Jun 2024 15:15:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1719148517; bh=em6xBacMcUkrM0ueEdmuGSEWcOK/kOxfWM1iE8Hxy7w=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=oZbYSDXqoOrt6iurhKhD4jvD+jwc6GBy+u1drDzPC2iYqY8cBhT7HwMRC6HRSx+L6 GC62MuxVMf3fP8K2aCKoiTk3LJu1f0Ytn/41zlx1BLDfJbIxyPtr7NZtIx9JP2v5ZF EWnEeicEnyWRQ8t02BHIW1XAumck2PTgOrujFArgxs6bSoWf4u2Yzs+20xJicfD1nr LT8Z8fQCfsaUUS5GUBGlS8zFyibJN7k8jQqvfAGCydVURYWrBijLdhDQx7OhixP9iS lJfdbHsj+qHeCw0JDft0+X7WlJPlYMdjRTKA9HLGN+0S6zZaK6WeeptH9I231beOJs el2wCCKbQMUeA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4W6WmM3xf0z9rxM; Sun, 23 Jun 2024 15:15:15 +0200 (CEST) From: Ihor Radchenko To: =?utf-8?Q?Micha=C3=ABl?= Cadilhac Cc: Jack Kamm , Org-Mode mailing list Subject: Re: ox-icalendar: Filter todo-types In-Reply-To: References: <874j9ko8uu.fsf@gmail.com> <87a5jbvqzl.fsf@localhost> Date: Sun, 23 Jun 2024 13:16:58 +0000 Message-ID: <87v81zu7cl.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.66; envelope-from=yantar92@posteo.net; helo=mout02.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.01, RCVD_IN_MSPIKE_WL=-0.01, 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-Queue-Id: 868833E1D9 X-Migadu-Scanner: mx13.migadu.com X-Migadu-Spam-Score: -9.58 X-Spam-Score: -9.58 X-TUID: 0w3CLpi9UQor Micha=C3=ABl Cadilhac writes: >> > Perhaps we could have an option ox-icalendar-export-todo-keywords-as >> > which could determine whether a keyword should be exported, and if so >> > with what status, e.g.: >> > >> > (defcustom ox-icalendar-export-todo-keywords-as >> > '((no-export . ("SKIP")) >> > (cancelled . ("KILLED" "CANCELLED")) >> > (in-process . ("PROG")))) > ... >> Maybe we can expand the allowed values of `org-icalendar-include-todo' i= nstead? > > I don't think this is the purpose of `include-todo', which seems to be > specific to VTODO vs VEVENT. Do you have something in mind that > combines that feature with STATUS? You are right that `org-icalendar-include-todo' is only affecting VTODO, but not VEVENT. My concern is mostly that "(no-export . ("SKIP"))" is somewhat similar to `org-icalendar-include-todo' set to a list of todo keywords. So, it may be confused with VTODO-specific option. Another concern is that we already have `org-export-with-tasks' where you can specify which todo keywords should be exported and which headings should be exported, according to their todo keyword. So, "no-export" appears to unnecessary. What is unique to icalendar exporter is the STATUS property. Having a setting to set it according to todo keyword would indeed make sense. However, after I looked at the RFC in more details now, I can see that the values of STATUS property depend on the entry type: statvalue-event =3D "TENTATIVE" ;Indicates event is tentative. / "CONFIRMED" ;Indicates event is definite. / "CANCELLED" ;Indicates event was cancelled. ;Status values for a "VEVENT" statvalue-todo =3D "NEEDS-ACTION" ;Indicates to-do needs action. / "COMPLETED" ;Indicates to-do completed. / "IN-PROCESS" ;Indicates to-do in process of. / "CANCELLED" ;Indicates to-do was cancelled. ;Status values for "VTODO". statvalue-jour =3D "DRAFT" ;Indicates journal is draft. / "FINAL" ;Indicates journal is final. / "CANCELLED" ;Indicates journal is removed. ;Status values for "VJOURNAL". Maybe we can introduce separate variables mapping todo keyword to status depending on the entry type (VTODO vs. VEVENT; we do not export VJOURNAL)? --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at