From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.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 wI5ZFlDgx2NhdwEAbAwnHQ (envelope-from ) for ; Wed, 18 Jan 2023 13:04:32 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id oLdaFlDgx2PPGwEA9RJhRA (envelope-from ) for ; Wed, 18 Jan 2023 13:04:32 +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 E2B1312296 for ; Wed, 18 Jan 2023 13:04:31 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pI7AV-0003fw-JK; Wed, 18 Jan 2023 07:03:51 -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 1pI7AE-0003Y8-De for emacs-orgmode@gnu.org; Wed, 18 Jan 2023 07:03:39 -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 1pI7A5-0005TW-P7 for emacs-orgmode@gnu.org; Wed, 18 Jan 2023 07:03:28 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 775B82402FD for ; Wed, 18 Jan 2023 13:02:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1674043342; bh=tK/CKW5U4CQThEwAIRHMN7PBfAT5wur+Dq74YCdqFSY=; h=From:To:Cc:Subject:Date:From; b=P0ROcui7BstvaX8Y3Z56tUK1djwCKJfeatO8Wr/BHAjlhgo5aJjCXaV+Ot4dukznM ltzJ1yoUbcEUjG/krZIFFE3rKRXhKS4ERUJV7EvJMq5BN8Kusf0QASc3sksNE5NsEj IxP2HQjh0WZmP306lk0fPeh0NSFCkSAxr25MH3/sGD8djk22ddEvqlWxWrY8KQy2rH F3M6X7OaXQqRkD6B9uGMCFvtWGjSlwP5B5cPjLkza5Gm6IyV7HTLzSJmkZajuRL8q8 /UdJ0fCAoxKS/yj8CuveMnQKnbC4mp3pebZuEupaM0lUpKJD7+LNo68VCMwhaLyCng VIayW+hpJJxKA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Nxks933dkz6tmK; Wed, 18 Jan 2023 13:02:21 +0100 (CET) From: Ihor Radchenko To: Tim Cross Cc: Daryl Manning , rjhorn@alum.mit.edu, emacs-orgmode@gnu.org Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda In-Reply-To: <63c7dd3d.170a0220.6b4d6.f84f@mx.google.com> References: <86zgamtv6o.fsf@gmail.com> <87tu0t1i0c.fsf@localhost> <63c2aa9e.170a0220.3bb49.9ef4@mx.google.com> <87pmbhz1x6.fsf@localhost> <87wn5mlo7f.fsf@localhost> <87pmbelnd0.fsf@localhost> <87fscajo2q.fsf@localhost> <87cz7ejmgu.fsf@localhost> <63c66048.630a0220.427bf.a5f6@mx.google.com> <87r0vtiks0.fsf@localhost> <63c671c0.a70a0220.61aa5.56b8@mx.google.com> <87fsc88aq9.fsf@localhost> <63c7dd3d.170a0220.6b4d6.f84f@mx.google.com> Date: Wed, 18 Jan 2023 12:02:49 +0000 Message-ID: <877cxk6oeu.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-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1674043472; a=rsa-sha256; cv=none; b=tvKFrMt5H33sS/GEnGKhnIkWmdUchAsPaCRwyOX1LX4FDZnrlG48It9AXiNlRfAxQrDwpi pkkMOVA8bJ5oU2OA0w1CDVT29S+kkuTo/KmPCXyerGvrmckXTUJPjzCR44qXUyM8KI5djb 3ACWPxsxLRxY/0jkCICQik7LUWJPsPA8SnpJMIWv6qJr27dz9Cx1qDaTMUQJNTLgdIv2+U f/XrTLKZf0O3QRTgfwnXdFZ5xhqFCqrGFI2kf52qlLhsCCKbrKj8FwlLtZBNhge5H1Rk3X X7ZxHeCmyaTkRS8LEUdeNzOG6M4/DNzJbjEzpPOfirFY3vh5RTycUJZEsLpoDQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=P0ROcui7; 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=1674043472; 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=4dqI5g3k2o8b90uxTkGnGray+3mT1aAeRAaH3Fza3P4=; b=dG4aCn0mtIsCpXjHDAlG5b2aRaDtzyCHR0/wvoMb1sLRBJT4g+/NEtXzQRnHMEdUPuhCYP jInXyTfIRFV2UhNiU+Ui5bHNp+U1xXD7oy+3RSdnDVC+YNlReL9hGk+HMJCPQVrN+R74CP eZqhH7+t945ISrVNrSNGMyuNIUYwxfq35LhVtFSdqme2yiTwZfeAnJeozANV6qqmenug0t hyWceeE8YoBXZZx9yoEEk7LHulAOklFymifCw/Oat0vI4Rf36Z8nilhccKqVXdidgsWcZ+ l403nE/zVakmQGgeL+/5m1sNHymSu/23/JR20E9OWKCP04P9gyr0n50QVbkZTQ== X-Spam-Score: -9.88 X-Migadu-Queue-Id: E2B1312296 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=P0ROcui7; 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" X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -9.88 X-TUID: DGIRg3wVKyI/ Tim Cross writes: >> Does it sound good enough? > > No, I'm afraid not. How does org distinguish between meeting 1 and > meeting 2? IN meeting one, when the timezone transitions in/out of > daylight savings, nothing needs to change, but in meeting 2, when this > occurs, the meeting needs to be re-sechduled so that it keeps the same > offset relative to UTC. > Some mechanism is needed so that the user can > identify timestamps like those fo rmeeting 1 from those for meeting > 2. My idea was to have meeting 1 type timestamps without TZ info and > meeting 2 require fully qualified TZ info. However, while this would > probably work, I don't like it because it isn't explicit and would be > prone to errors. I still don't understand. In Org, you will have a default time zone that will be used to build the agenda. In meeting 1, you set the time zone to your local zone In meeting 2, you set the time zone to the time zone where the meeting is scheduled. The, both the meetings will be first converted to the default time zone and appear in your agenda adjusted as required. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at