From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 4K7MElIfO2KbbgEAgWs5BA (envelope-from ) for ; Wed, 23 Mar 2022 14:23:30 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id IOIuEFIfO2JzdAEA9RJhRA (envelope-from ) for ; Wed, 23 Mar 2022 14:23:30 +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 11A88125FD for ; Wed, 23 Mar 2022 14:23:30 +0100 (CET) Received: from localhost ([::1]:34724 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nX0xU-0003Zq-Po for larch@yhetil.org; Wed, 23 Mar 2022 09:23:28 -0400 Received: from eggs.gnu.org ([209.51.188.92]:42284) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nX0nk-0003eF-Ph for emacs-orgmode@gnu.org; Wed, 23 Mar 2022 09:13:25 -0400 Received: from [2607:f8b0:4864:20::536] (port=46625 helo=mail-pg1-x536.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nX0ni-0000Mq-Ng for emacs-orgmode@gnu.org; Wed, 23 Mar 2022 09:13:24 -0400 Received: by mail-pg1-x536.google.com with SMTP id o23so1070622pgk.13 for ; Wed, 23 Mar 2022 06:13:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=YgdUC+IxIsxnI9rJkVybissSD/lzmIOsEjH+71b5MKE=; b=dVg4l7WlwFY9uvAj4IDUiP7tDklVp9RW1uCsMIneBHfNBTi8KrcV5EfGEVQgM1MqYG 5nDE61Aqr25Z7AUekFMVaVIaU2VYDHAk3SeJQxOY/kyMcLHoeGJTYZZCF1F/lZ6gzr0b qPFrG2s7tCNtixrMXxuJouMUmcUA85Wc/UAp8kcODbN8ITFYEOr512Dc1cvXt63vpx8t a95lSC/SHe4J+7IMTqPJZw+hEVlyqQweEGvwVG7yzmdHrcobrxfCTii0WCWZqPawRaay j54GW08yiuvw/867tnF9ORIxn7kbRY9uig7Tx3DZkxgD+aPo2N1y6MCllsm6euyvPUb1 uvkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=YgdUC+IxIsxnI9rJkVybissSD/lzmIOsEjH+71b5MKE=; b=W2oNmN+cbADaFP5Lwk5QVu7CFkaS+HXTYchA+QjOtFjYp+uIlULHfNlPuxH674fOzm PWcbfZnJPbqViIwwZmGSEgYc+FRY0TLV0nDL0flqKPWHH0Dpqe/O77/8FuF6mfIEYGsS kouG741nI0NtC3ghpXTkr++E8Ccdmz0ySfopyADHyYvcC38H9+rOYDxajkr5r68gAG79 +BvISFzWnMDJVtc0f9nbSwd9njG5rtMp5VSx0siN34YRFYglxnbq+nHcVUPdJUDShs+A 2zrixw/OuK1JtcEHLphVNKuJMZDFER9RdCoG806NffDy+2WRWgWeOzPGwVXnCFRjz9yR e0zQ== X-Gm-Message-State: AOAM533iYH2iEyM8IsRRInxyMhZehEhpsPYR1iGjKslkq+7KgDfFlfMh JvSxu/IbeTSAFYTiQZmMrF8= X-Google-Smtp-Source: ABdhPJzi+fORMQrdx4v+KeqayqZLe4dziky0oYLiKGuPlGXphwk6tb0n89bv3LZjjE/HtoZiXkGkOQ== X-Received: by 2002:a63:6c01:0:b0:37c:73a0:a175 with SMTP id h1-20020a636c01000000b0037c73a0a175mr25372130pgc.415.1648041200702; Wed, 23 Mar 2022 06:13:20 -0700 (PDT) Received: from localhost ([209.95.60.92]) by smtp.gmail.com with ESMTPSA id p125-20020a622983000000b004f6c5d58225sm26536984pfp.90.2022.03.23.06.13.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Mar 2022 06:13:19 -0700 (PDT) From: Ihor Radchenko To: Tim Cross Subject: Re: Timestamp parsing inside node properties and other contexts out of org-element-object-restrictions (was: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]) In-Reply-To: <87pmmdsm2f.fsf@gmail.com> References: <87v8wje4nd.fsf@localhost> <066001d83d3c$7b463380$71d29a80$@tomdavey.com> <87tubqmi94.fsf@localhost> <87r16umhnj.fsf@localhost> <87pmmdsm2f.fsf@gmail.com> Date: Wed, 23 Mar 2022 21:13:42 +0800 Message-ID: <87y210stfd.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::536 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::536; envelope-from=yantar92@gmail.com; helo=mail-pg1-x536.google.com X-Spam_score_int: -3 X-Spam_score: -0.4 X-Spam_bar: / X-Spam_report: (-0.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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, PDS_HP_HELO_NORDNS=0.659, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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: , Cc: Ignacio Casso , emacs-orgmode@gnu.org, tom@tomdavey.com, Nicolas Goaziou Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1648041810; 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=YgdUC+IxIsxnI9rJkVybissSD/lzmIOsEjH+71b5MKE=; b=d2L25OLUKnVznuIH4ErvtapX3/fk2cHEK+sVwhQ8/wnhk443zU1ynORGHXwd2pQF+GW2Nw LjtURsLxWsNv+ETsho9KyoKp3c/sdW3bWRB48fxvrfS+QSYvoMrio5ObbEjFCur9pvsniV t1W5CRgk660kHqD6f2HAUaRuHPjGIj3Gw+61RGZ+J/f0waJJ0a0/GqGQKKhOuMhiIbdHFJ 6T8I80cdHCheiwE32zIOexa8HukOfytn7+OvGdoa3G9BtAD1H0lrin9JS5qF0VZReIhNcs FqZF8Z6IDks+6XSak4NXr5qFnbOiBhc2mfFtB1oYFR/ts8HfEQgrtw2PufNOLQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1648041810; a=rsa-sha256; cv=none; b=BrwF4S7Bt6Bc9Y/ig5KsqICn/OW5VTM2bkae251rgFOIr9fwAM3z74l6B1hZuBkHmmasFi n3YK8yEkkBB4TY8VdawWMckfSZuIcL21AJ6G6uJbxszwL2fdzf4zXRChNv6lQgJLgU4no8 aOFK5IvhyW3514hx8bET5YIHOAatu7a76X25DAZtA2l0S0H6zsA3eUS/cuLVYoeRfNnloF fmaRZn+eD/X2Son7Uk5RPFK27WiP0G8wrG9uPNYxduwft4yI4e7DQaBLDkQI35kM/lLgZ+ 0AYEDNoswmziGyJ4ioao/v84HAiKn35P8SdYhAiTopPHB8fku4/vRnlI11Uy5Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=dVg4l7Wl; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); 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" X-Migadu-Spam-Score: 8.46 X-Spam: Yes Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=dVg4l7Wl; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); 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" X-Migadu-Queue-Id: 11A88125FD X-Spam-Score: 8.46 X-Migadu-Spam: Yes X-Migadu-Scanner: scn1.migadu.com X-TUID: za3czRmr6Eai Tim Cross writes: > I think we have to be very wary here. I can see any changes here causing > lots of breakage for people. I know for my own use case, I use > timestamps a lot in property draws and various source blocks. I never > want any of them showing up in my agenda. FYI, the default agenda behaviour around a month ago was exactly what you want to avoid (assuming that you use active timestamps). I explained in more details in https://list.orgmode.org/87h77psaik.fsf@gmail.com/T/#me4f41a8b36ada384d87cf028ef10164dfa526ad2 Let's keep discussion of the original issue in the original thread. > Unfortunately, I think org timestamps is a bit of a mess and we need to > be very careful about further complicating matters. The inability to > handle timezones is a major limitation IMO. The inability to handle > daylight savings transitions in a consistent manner (particularly for > calculation of periods, duration, etc) is often a source of errors and > if you are unfortunate enough to regularly travel across different > timezones, forget about using org mode to manage your schedule. > > I have done several deep dives into org-mode's timestamp stuff, but > usually come back up gasping for air. Managing data and time data is > often far more complicated than it may appear on the surface. I think we > need to be extremely conservative when considering changes in this area > (it is the main reason I've never managed to find a way to add time zone > data - every solution I could think of was either really high on the > level of breakage and frustration it would create for users or it > adversely impacted the convenience/usability of org timestamps). I sympathise with you. I still remember my struggle when I had to travel across multiple time zones. Anyway, the timezone issue have been discussed multiple times within last 10 years or so. It is complex and nobody managed to come with a good idea how to approach it. Best, Ihor