From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1.migadu.com with LMTPS id OL3cKFWoSGb9tQAAe85BDQ:P1 (envelope-from ) for ; Sat, 18 May 2024 15:08:37 +0200 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id OL3cKFWoSGb9tQAAe85BDQ (envelope-from ) for ; Sat, 18 May 2024 15:08:37 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=noM0nfID; dmarc=pass (policy=none) header.from=posteo.net; 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" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1716037717; a=rsa-sha256; cv=none; b=hzPa/hz6qkhu2w7CzphlktF1pIzE198of3dP2kNvak5tZPaIcMNMZacvqqnnUv6bwuauOt 0L9oGiygKlDQoUJQZFhiaEJ7rrTpO/Hac0xBGtydvNXV3RiHgayJJ1eg8T2V8j3e3ptq9e xUTq1jzfXwcIWaoAKw+tMMDY5Q0r17At+CnJOGJ3ceBQIVZo9Y+8GzCpkfxaQtK3Jv/TFM 8X50ED0CMS89ArCJ2gc1dmNgbu69Sj9IklRW1JKmNOXKHbQA9E3XwzWhhSHgOPovE9hmP3 G2OF14I50tHuqhAKFN8CuOrW3P/mQXXDWaCUyocRSQcnh5s6r+albtBs5puXnQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=noM0nfID; dmarc=pass (policy=none) header.from=posteo.net; 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1716037717; 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=2YbE3/uEHsevuuwvcqgabgct6o17Q4L/jpw52epU60w=; b=L3nu/GVx4MAoO2DIizO4/S6Oa28s5hr1t2hTMfA3ienX8Kxxvp2oqx2/VhHrl5iC6ulQ8u jx9PlU4JgmWXZP8yUoHt8tf3TrafmdtQMw4BVNhf7tqBTfUaFeUSr5DYWLiMkwfGVPzCf3 2xm1VmyXRzqJEtAoHhEY8MlRTjFwV8G8F32vcKXs/1lA0Q/SKTbpFqgt0WZDKfKWB6hrC6 g/JZt4Pwjt0gwOjO/4CmKL7HWx374JzBnw15ICacWVGVN8fX22m9if1K6Q/DqnMQGQx6pe KsFgGm4BPlHF1X2VbqyolCGg39Bi8ARBql+4whJO5SmglyHqT0adqaEWqGUBqQ== 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 5954E14CDD for ; Sat, 18 May 2024 15:08:37 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s8Jmi-0006Xw-Id; Sat, 18 May 2024 09:07:36 -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 1s8Jmg-0006Xd-CP for emacs-orgmode@gnu.org; Sat, 18 May 2024 09:07:34 -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 1s8Jmc-00033U-29 for emacs-orgmode@gnu.org; Sat, 18 May 2024 09:07:33 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id B376D240101 for ; Sat, 18 May 2024 15:07:27 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1716037647; bh=xnSxc4y5jEmpvCHlui5am1PWbOlYd24PFMZRhQUYWdw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=noM0nfIDJoS20Dqu+ilYR5nX4B8rfMkr8CrKs5szsdPEQGixPNMoP32O5lVphrGd6 2WtOSlwgXmfHRhQy96VMHK5MhnX4R3WQyivvU0XY7zMe9+eB01N5YkA83FN08FkcvO 5KhNJlpOilnbqlJG/whbziCEBQ3wF5proTpkDCWnwt6W18QbvPCI36bsGzE/K+tQzC ug/6sbEUJb2HN7DpQ53PeNGxbwHUQULkCkdu7bVZCe7lO0tzkY6oeIVjtEvFoV7sil GqrzzwGdMkEJTByY/yFKp8Gh+7XHU0vwgO1mHbGloB6/JWSgEN742Zm+sNSO7hdfN3 g2QJGM5mtEnGg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VhPHy6Gs5z9rxK; Sat, 18 May 2024 15:07:26 +0200 (CEST) From: Ihor Radchenko To: Stefan Nobis Cc: emacs-orgmode@gnu.org Subject: Re: [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?) In-Reply-To: References: <87frvzodze.fsf@localhost> <87v83if2io.fsf@localhost> <87seykpn58.fsf@localhost> <87cypjtkke.fsf@localhost> Date: Sat, 18 May 2024 13:09:03 +0000 Message-ID: <87y187s1w0.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_H3=0.001, RCVD_IN_MSPIKE_WL=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-Queue-Id: 5954E14CDD X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -9.58 X-Spam-Score: -9.58 X-TUID: 9a6qSAPD3mDa Stefan Nobis writes: > Ihor Radchenko writes: > >> +1m! is awkward - what if [2024-05-12 +1m!]? > > You are right. I have not really spent time to think about a nice > syntax. But I think it needs to be encoded in the increment part, not > in the date part (because after the first increment, the information > that we want the last day of each month would be lost; and always > using yyyy-(mm+1)--1 also seems a bit awkward). It does not have to be lost. We can adjust the repeater function to handle negative dates/months specially, so that [2024-05--1 +1m] -> [2024-06--1 +1m] > So maybe "+1mx" or some other way to encode "go to last day of next > month" directly into the increment? How does it make my example with [2024-05-12 +1m!] any less awkward? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at