From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id Grb5D8d4xmNCVQEAbAwnHQ (envelope-from ) for ; Tue, 17 Jan 2023 11:30:31 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id mKUsDsd4xmO1MAEAauVa8A (envelope-from ) for ; Tue, 17 Jan 2023 11:30:31 +0100 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 21C19C3C9 for ; Tue, 17 Jan 2023 11:30:31 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pHjDt-00066J-04; Tue, 17 Jan 2023 05:29:45 -0500 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 1pHjDq-00065c-FS for emacs-orgmode@gnu.org; Tue, 17 Jan 2023 05:29:42 -0500 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 1pHjDo-0007Li-8g for emacs-orgmode@gnu.org; Tue, 17 Jan 2023 05:29:42 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 58CB32402C4 for ; Tue, 17 Jan 2023 11:29:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1673951378; bh=44FFu5mbc1JO/9CTNDMCuTb5KHyeTxVcXip8dzEv/Qs=; h=From:To:Cc:Subject:Date:From; b=Ing6XVM0Cua/lJj66rCmn6lArf7XQUnTCcnKYmz3T04vDnKat8GR8Zqof+qNZp+fV AF6f/HQ7CKdas9/1QRh7Qo8yfkQXOxawOlwIfuLzJA/SJk+UrHyZUdrzFB+NZkxzBG N0AcVpFjapS6ONT5aRLmP1OX3VauwWT4nxN3HGuRPIc2Ry6Kph6dHK/GgNIW3OpKsi KaxMAjlVx+9GYM4f9SkJWJ7bSUYBZ8zglBkNH5ghnYskG4p0Tg5BrxeIB+8hQXX9S0 as8n1RIj2GRyTa3TJNZVA10hhFz3CdSw1XGa/Vh8wiiDpAuOrQBAMlX64Ly4PiguuK Ul+xMGkxbTpVQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Nx4rd3RMgz6tmH; Tue, 17 Jan 2023 11:29:37 +0100 (CET) From: Ihor Radchenko To: Detlef Steuer Cc: emacs-orgmode@gnu.org Subject: Re: [patch] improved: add TTL as defcustom to ox-icalendar In-Reply-To: <20230117110316.56a1899e@gaia.unibw-hamburg.de> References: <20211230225919.1a660666@hsu-hh.de> <20220102142849.0af72bcb@hsu-hh.de> <20220103084141.72d2f384@hsu-hh.de> <20220103123253.6bb48655@hsu-hh.de> <87o7tgaa42.fsf@localhost> <20221109082520.066dc4c6@linux.fritz.box> <20230113181035.1469ab37@hsu-hh.de> <878ri52z06.fsf@localhost> <20230116234230.5080fb07@linux.fritz.box> <87lem1ijih.fsf@localhost> <20230117110316.56a1899e@gaia.unibw-hamburg.de> Date: Tue, 17 Jan 2023 10:30:07 +0000 Message-ID: <87a62hihcg.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain 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_H2=-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-TUID: BuxLI+r1QAVk Detlef Steuer writes: >> The patch only allows to the TTL globally for all the calendars. >> However, it would make sense to specify TTL on per-file basis. WDYT? >> > > Hmm. Surely it would be useful to have the option to use different TTL > settings for different calendar exports, yes. > > The next question would be, if org-icalendar-combine-agenda-files is > called and the files have different per-file settings, which will be > used? The only sane way would be using the global default. > May be single file org-icalendar-export-to-ics and > org-icalender-export-agenda-files use an existing per-file setting, > global setting otherwise, but org-icalendar-combine-agenda-files always > uses the global setting? Agree. To achieve this you just need to update the export option settings: (:icalendar-ttl nil nil org-icalendar-ttl) adding a file keyword to be used. See `org-export-options-alist' docstring. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at