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 uOeSJ+3FXWfi7AAA62LTzQ:P1 (envelope-from ) for ; Sat, 14 Dec 2024 17:52:45 +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 uOeSJ+3FXWfi7AAA62LTzQ (envelope-from ) for ; Sat, 14 Dec 2024 18:52:45 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=renaudbussieres.com header.s=default header.b=MjbI43cZ; 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=gnu.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1734198765; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=RaOw31QMk1URv9ijvlwj6ZsY1WHUbalcQLwaClU8vs4=; b=ITCbaDoKxvlSV1M3yCZ2zEUNjj8CNuJuJ5p7xPckEZqnFA1RJn4WXeIE95K4vKk0epNoin OCvBR8Wb0291QZYUH9XW1B2kbwCPcg2XPyB2+0gweb03iBSreNL+z8rDWzB2tnIQEl1spb dVAvpqN7yLF0biryf5KZQ+G4HPTRwHr/4f/VYFY7Q9EGmsGsxvb+oI8px5fp/asH4DQZ8b Nkco7Ivoc0e/v/J083ytnmO/xCdDvEAQ8Fgz9XOit+irR8/y1vEUWge9QhzZSRkrdQ6xTS 3McB/MlDupjvuRnCQARzj7ESdfNWYfNc2CvpTdATkt5Yb5ERI64r3jMpPGzANA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=renaudbussieres.com header.s=default header.b=MjbI43cZ; 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=gnu.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1734198765; a=rsa-sha256; cv=none; b=TBVxKvxeTzvixl73zoBYZiJCGSf0jgSjt8kau/HXoRvhEyL9n0OvLLWCrUY7h6zbakz8/0 Pdf7935tKoqtqid2jAPbREk+w9S+9ykh4giw3r5sILhSn1aOExS2htAxteSjMpXPfXRUqp Qq+MVoqR/YEPBlKOmT6Asxe4yC+Q94XM+HRhsGT6w7/G5b3EMvcB5U6oIrfr3uYU/+4hZW u+Tsxhp/HRIBPCjDlFT++IRuzBnWn1mCwQjaAk2+F+A1QtH1sj7vBrg7spRUKv4Khhw64Z f8xWHuFIlLwixnFiVpMX3UPZ3FSnQOhnZ1M1v4V8aILb5chPCmcG0zn8PqZApQ== 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 7BC1B7E2D6 for ; Sat, 14 Dec 2024 18:52:45 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tMWIn-0003XI-Jf; Sat, 14 Dec 2024 12:51:41 -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 1tMWIl-0003Wt-TV for emacs-orgmode@gnu.org; Sat, 14 Dec 2024 12:51:40 -0500 Received: from seout9.web-dns1.com ([67.215.8.20]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tMWIk-00029O-9S for emacs-orgmode@gnu.org; Sat, 14 Dec 2024 12:51:39 -0500 Received: from viger.whc.ca ([173.209.38.98]) by se3.web-dns1.com with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from ) id 1tMWIh-003u6U-2S for emacs-orgmode@gnu.org; Sat, 14 Dec 2024 12:51:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=renaudbussieres.com; s=default; h=Content-Type:MIME-Version:Message-ID:Date :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=RaOw31QMk1URv9ijvlwj6ZsY1WHUbalcQLwaClU8vs4=; b=MjbI43cZsXJIuTa5gh/OSUwdQg 2xRYllgH8JQXFSV96LBEV8EPrXiiE+rnQscLuHFlaql4dHwHzkc+9TYUAWh8K0S7SqRbq+N2Qxw83 tC7RB7KHPPxjwFEhMDF8TLv3RvaOapK1x+dgAEhbyH3QEVGMTNiIu9d2uVXhVjfaA71jm8dLvg3uI J/qdyOkuQOAVVkKmMMuJIbK98vbhJa/WagAjCKU3U84a/jDkQ2ffQDx7Znw6heDdVhmh43cyaD8Yh bWgxRkJKADBVHtl2QNSYBBJMs76G/9DOVCJvzTrheiiDq6Jo7SamkMyuQox51cYOkydnreXwDAJhZ x+grTCCQ==; Received: from [135.23.198.195] (port=42810 helo=localhost) by viger.whc.ca with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1tMWIg-0001cG-11 for emacs-orgmode@gnu.org; Sat, 14 Dec 2024 12:51:34 -0500 To: emacs-orgmode@gnu.org Cc: Subject: What's the proper way to define a recurring event Date: Sat, 14 Dec 2024 12:51:33 -0500 Message-ID: <87bjxe2lwa.fsf@renaudbussieres.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: 173.209.38.98 X-SpamExperts-Domain: out.viger.whc.ca X-SpamExperts-Username: 173.209.38.98 X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.30) X-Recommended-Action: accept X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT/1afTefDdAKhQHvcPNl9b7PUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5xiExUbNqvmdkLSOzf1W2Y3z8hkeSqZT0W1YMl0fRDa99cV PSoHm0W/3adFfiYl2nuSffpkNyykoqHWnEZw8bWt/T4GcPvCLvSpAEEGy7kYxtLSm6ZPIIlKlwTC gIG9Jyw9W3J8DjtrYUCcjc2kRLvhYOokoNyi5mJBlH5XrbxRrs4Mvl+RIe6zaX9Xo/eYapbhFICu rO5GrHxvhcBIPS3XvRkWzsAgaWolxIxCj2GHto6atsxaFkWS/KO9ggVt7y11v0HCq9Ij3WgoQoez M+scYG4yYBh/iFtUTfPc63fdkJhq47NBgtiICsD9EhSg+JMKt+3LqRhD13oJjpl5+wRGT5hPjouz Ch0cLMYM4sAH2hUdFqkFA+YKkUlydLh5cSaHt73jJKU44zPi+Pzpc9G5zUzrdZU7OhwXeH7YLZxC jR6PhaTR43zax8ELeq9TpqTLgKffTIgl7nuGO/IJU1342OUMeHyTpNN0eXybX/w7/4a+Zyc1sUYl ckMDbruAhxeNNwwkljQwv/BVv434ElpDBtt0s05YqTfD9fnGa90+VKOtkYHoZPeh00ZdYDqvSOxV EhlIUChD+H4i8zkc9GtHhNElOrkhMvUFKo/SRxkiu7EvxDiMRUtiZfDHH77eFYjqfsc11bjrKRw5 PlQR5whiBqjgYNuilyhnSLWeXMyukk588Xm/mXJ/iWEjIdjMCy/qKC5qmv5oJDB6ysCXPb1OfIwN ViNW09Uw+Kd77OjoVw5Vxm/bnhrVKymAutkEJf+G0qtjud+v5myOgHhci98Dw6nIoDr0sXUZ7YZo Z/GZ+m2/vBgu0rMZ9H2qZ5N14T8k/ShmP1lfbGKu6ZAZN7W5ybSUPyS0vEGYAQEOah+dk9EuLl33 jYeStCVJd7Ee3vearKdVFoNjjiGpFC0Gf/N8pbYyrkE9YpQKUVPxC3Tx6A== X-Report-Abuse-To: spam@se1.web-dns1.com Received-SPF: pass client-ip=67.215.8.20; envelope-from=contact@renaudbussieres.com; helo=seout9.web-dns1.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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: , Reply-to: =?utf-8?Q?Renaud_Bussi=C3=A8res?= From: =?utf-8?Q?Renaud_Bussi=C3=A8res?= via "General discussions about Org-mode." 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 X-Migadu-Queue-Id: 7BC1B7E2D6 X-Migadu-Scanner: mx13.migadu.com X-Migadu-Spam-Score: -5.72 X-Spam-Score: -5.72 X-TUID: 2J1V71VTl6DL Hello, I've look around, and I haven't found a way to achieve the result I would like regarding recurring events (and not tasks) Let's say I want to insert my yoga class in my Agenda. This class starts on date X, it is planned to repeat every week, for 8 weeks. In my "agenda.org" file I would write: * Events ** Yoga Class <2024-10-07 Mon 16:00-17:30 +1w> That would display the class every week, but forever, that isn't ideal. If I change the timestamp to: <2024-10-07 Mon 16:00-17:30 +1w>--<2024-11-25 Mon> Then the event will appear in the agenda every day between 2024-10-07 and 2024-11-25, that's not right. It seems like time/date ranges do not respect repeaters. I know one way to do this would be to enter multiple timestamps, or multiple headings with timestamps for every occurences of the event. That would be manageable for my yoga class example, but that wouldn't work for recurring events that are repeated for a large or unknown number of times. Right now, what I can do is follow my first example, and when the recurring event is over, I archive it. This is fine, but still not ideal, because until I archive it, the event appears weekly forever. If I'm planning an event in the future, I would have to remember that this event that appears in my weekly schedule should not be there. And when I archive the event, it also disappears from the agenda history (if I look at previous weeks, the event isn't there anymore, because it is now archived). So I guess this question is also a feature request: It would be nice if Org-mode could take into account "repeater" while implementing time ranges. If no repeater is set, the event/task will appear every day during the range, like it currently does, but if there is a repeater that says, for example, +1w, then the event/task will appear only once a week, on the given day, in the given time range. Thanks for your time and support, Renaud B.