From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id 2OFOC7xDxWPGfQEAbAwnHQ (envelope-from ) for ; Mon, 16 Jan 2023 13:31:56 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id IB5JCrxDxWPfQAEAG6o9tA (envelope-from ) for ; Mon, 16 Jan 2023 13:31:56 +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 BF0FFD613 for ; Mon, 16 Jan 2023 13:31:55 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pHOe2-00021f-Fe; Mon, 16 Jan 2023 07:31:22 -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 1pHOdz-0001iR-Rf for emacs-orgmode@gnu.org; Mon, 16 Jan 2023 07:31:20 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pHOdx-0003jl-8T for emacs-orgmode@gnu.org; Mon, 16 Jan 2023 07:31:19 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 2182724015C for ; Mon, 16 Jan 2023 13:31:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1673872275; bh=xtsPUiVq8Ge1dg4LSC9j3zElxJETpUiXizIm/sTB30w=; h=From:To:Cc:Subject:Date:From; b=QbK08TW98pRHxqRnVGq2d8JwmYUY3Mx/Hdi72HQJL1iTEZFtdOs+pouBxhJnuDdJv OfoVXJtfDYMMVHezaBMNLsJV6689M1/4RGxa4AGdaehVRa9AxdPOFU2Rz1DCeEA2m6 CnqSUEWVaXa20/rjfn8Ra55y6d3LT5VlT3hTUBcDMFbdNpEB9LuzS4Gwe4YOIc5AUZ EN7I6TyJMxjGziEL2Jjduo7DD1A7luoltgt/BZg9LE6HNJWWttQgoxj5+pkbkSWlsb A9QfoDTs8Kpz8UpH7w3hC0w45sBeOHHhx2F4kIeS02ODwXZCGUus+wqbOU7Dw2SSB+ m7Dz9bekJvI/g== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NwWbQ1rxlz6tmN; Mon, 16 Jan 2023 13:31:14 +0100 (CET) From: Ihor Radchenko To: Tom Gillespie Cc: emacs-orgmode@gnu.org Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda In-Reply-To: References: <86zgamtv6o.fsf@gmail.com> <87tu0t1i0c.fsf@localhost> Date: Mon, 16 Jan 2023 12:31:40 +0000 Message-ID: <87mt6ilkyb.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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, 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 ARC-Seal: i=1; s=key1; d=yhetil.org; t=1673872315; a=rsa-sha256; cv=none; b=UPNjjTiPcMbbVXkRJxbzQBlgoXnX4qUPbxtG2YlLLby1tdmOLtXUDMUrfTjegi1MyRG4Np pZybLxTFhycbnZ3VO4t1cUz7EBeJzDt1MSx8WQQ6V/gOOck7gqlGTHkbQA37rFjPQ3IslA qPdzHvTEbrVjDnTizQoBjD2ER0J4MbRN2J5ncgzKwTfaT4aObR481j9r4qpKB+RO1WcwJ+ vRn5OQheKqW7LAjfakGd+7nobcAOTe+XenuVfkAwba5ucxnH56QfIG1TJhO8W1/8REfm4V CRIedaoXLQ8BTK1D5boJ1pqX8EVygWb9FuwUqMxmCBNIoS/DDHqdnMpHGYKOag== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=QbK08TW9; 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=1673872315; 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=sjsDEAFioUGwcLHsNWy8KioUiy8TPzO8blZPwFSn1so=; b=KJjNGnYDHHerbkd3mlj5fhn7kCl0fR+ORPkGbGEImKa7mljJl57e5ap3Oesv6oPY+F2Cke HZxfGZ8C3ARyqF97YJtI3tCVwYXKV6yEYC4Kx5IwZLa45yvkcoTmuT9+pjyRNUfawPL16R btnJPXrK13iCBWwxvcSTq4mWwRgtqZHbtb9MYbW4PEXqONl+nKJBBsu4AYk7cqtycDbr/K rEMp+A4sWTmq9TUhVOjw+r7NlVgY5ZMtynJkqeXMPE1AilNNgc4S/h8j4EQPrF3jPadSxj Q9GkNAkqlH2KdMCZc45zXtEnoBHjzqW5P1PLxf6Kunzq/Yx2ese9jLVeJC44Gg== X-Migadu-Spam-Score: -6.07 X-Spam-Score: -6.07 X-Migadu-Queue-Id: BF0FFD613 X-Migadu-Scanner: scn1.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=QbK08TW9; 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 X-TUID: yIKu/DOIcFnI Tom Gillespie writes: >> Note that REST imply that almost arbitrary suffix can be in TIME without >> braking the existing Org timestamp parsing code. > > I'm not sure how I feel about the REST in the grammar, I think it is a > reasonable approach but need to double check. I'm worried that there > can be some nasty interactions with REPEATER-OR-DELAY syntax, but that > may not actually be an issue. The existing code uses `org-ts-regexp-both' and `org-ts-regexp0' for analysis. + `org-element-timestamp-parser' that is using Elisp logic. And these requirements are pretty lax. The actual parsing just requires YYYY-MM-DD [day] XX:XX[-XX:XX][optional string containing anything but "\n]>"] with repeater and warning located anywhere after the required date/day/time components. date, repeater and warning periods do not have to contain " " afterwards and thus can have arbitrary misc data. This feature is used by org-habit, attaching things like /3w after the repeater. We have a lot of forward-compatibility in timestamps :) > I will note that this doesn't address the issue of syntax for > historical and future dates. For historical dates those almost always > require significant additional metadata to compensate for things like > the julian/gregorian calendar switchover etc. for future dates we may > want to go ahead and specify something beyond YYYY-. This is somewhat orthogonal to time zones. I am not sure if julian/gregorian is handled by system time libraries. It should, no? As for years BC, <-0001-...> will be a breaking change. But I do not think that we need to really worry about this. Not unless we actually get feature request. What is the practical application? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at