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 eBLIKhp+y2PiJgAAbAwnHQ (envelope-from ) for ; Sat, 21 Jan 2023 06:54:34 +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 +Kq5Khp+y2Nq0QAA9RJhRA (envelope-from ) for ; Sat, 21 Jan 2023 06:54:34 +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 463EE3F4E2 for ; Sat, 21 Jan 2023 06:54:34 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pJ6ox-0005h2-VQ; Sat, 21 Jan 2023 00:53:44 -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 1pJ6ov-0005go-NO for emacs-orgmode@gnu.org; Sat, 21 Jan 2023 00:53:41 -0500 Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pJ6ot-0007N4-UD for emacs-orgmode@gnu.org; Sat, 21 Jan 2023 00:53:41 -0500 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pJ6op-000735-Sn for emacs-orgmode@gnu.org; Sat, 21 Jan 2023 06:53:35 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Date: Sat, 21 Jan 2023 12:53:27 +0700 Message-ID: References: <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> <877cxk6oeu.fsf@localhost> <63c86454.170a0220.80970.652d@mx.google.com> <63c8f5a6.170a0220.ea8cf.7f96@mx.google.com> <63c9b654.170a0220.d82d2.4254@mx.google.com> <87lelxk87a.fsf@tsdye.online> <63ca5101.630a0220.b2298.3363@mx.google.com> <87h6wljhce.fsf@tsdye.online> <87cz79j5gu.fsf@tsdye.online> <63cb3036.170a0220.3ea60.3a93@mx.google.com> <878rhwk8jk.fsf@tsdye.online> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Content-Language: en-US In-Reply-To: <878rhwk8jk.fsf@tsdye.online> Received-SPF: pass client-ip=116.202.254.214; envelope-from=geo-emacs-orgmode@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 29 X-Spam_score: 2.9 X-Spam_bar: ++ X-Spam_report: (2.9 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.089, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_CSS=0.1, URIBL_CSS_A=0.1 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: , 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=1674280474; a=rsa-sha256; cv=none; b=eNQ4x4Pupy26zguePe+14zOlNsemoc9dp/6y8mgLj585JR26YBC2g6qEP+KHWxc8sgL2B7 CwdttaGbiFqcqPYAkxHPhIVjMuOy0B9IZXMLJhwuir4LOGqOka77LlauLTLxk7GqIkaqPo Ww/W64BbKZWW3fS9ouO7FHEZUzlYPGTBMW0gUu5QZ2Ccm3wD6Vd1AoSAOdyNoQh0HU2tKx vTHsEFeUSKzO8w+5dZU/VUfZskG6bZ4MfzhzsUThd+LQOFtmdQK4tkgE0Y9LOi6DgI4INc qqkPukIQnZdWS5KtcSFNKZ+hVd+lT3y7Dm8YeI7Mo5/DgNjTIz72Qlz1qheUPQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1674280474; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=dYJwLSxqy6WK+o7RKekhaK3a9UC4zIxZGkKJAqVGsB0=; b=V/+porSqLMJp84iG+TLansFBlsZ7lhxl6s+5Fkqjc9TWa4QaeGKErpdPLqMhdI1sQTOMGl 7x4fKyd/5rOxAFF5W7zkV/NYTbyPKKQiRtoj7y9Z+/U9i6mOpFgrMztlrr0o71pTc7/VtY JtujssBtON7SqvEzsJsjRT14JxaL7W3yNIUZVq3oN93AXYgFRT5ib5I+4xnjP6diS0Yi/b rbVvfB/A4dZOLfyfsxvCLeSnlV2DbU4quZNb/VCdVzytCzvzGG4/9CoC5wa5UrVm8XKVkN X9p5V3WloLTWSeeIbMcxSd/YgtvO5lVelsUBSDV9jg0Njgx+pirDRTafCmEEVw== X-Spam-Score: 3.79 X-Migadu-Queue-Id: 463EE3F4E2 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" 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-Scanner: scn0.migadu.com X-Migadu-Spam-Score: 3.79 X-TUID: 2TpStlV+ekBL On 21/01/2023 07:37, Thomas S. Dye wrote: >>> 1) Occurrence, where the timestamp includes UTC; >>> 2) Event relative to user, where the timestamp does not include UTC >>> or a time zone; and 3) >>> Event not relative to user, where the timestamp includes the relevant >>> time zone. For a while I prefer to concentrate on future timestamps and postpone discussion of ones in the past. As to format for storage timestamps in Org files, particular timestamps may have or not explicitly specified timezones, but it is unrelated to these 3 cases. It may be convenient to keep work.org file with TIMEZONE keyword for location of the office and do not specify it for each timestamps, so during a trip it allows to see correct time of regular meetings. In addition you may have personal.org file where most timestamps assumes timezone of your current presence. In both files some timestamps may have explicit timezone either "local follow me", UTC, or for particular location. From my point of view these, 3 cases might be relevant to date-time picker UI, but not for storage format. While parsing, interpretation of each timestamp without explicit timezone depends on preferences chosen at higher scope. > Or, it might be a recurring virtual meeting that the boss wants to > initiate at 9:00 AM her time, regardless of the time zone she happens to > inhabit, as might happen on a business trip. I believe that some manual action is required in this case anyway. You almost certainly already have 9:00 AM in your agenda as a reoccurring timestamp either with implicit or explicit timezone of usual presence. For the period of the trip it is necessary to add series of meetings with explicitly specified timezones (UTC or locations during the trip). Another approach is to define ad hoc "boss" timezone and update it to reflect all trips. At the Org side it might be support of multiple ad hoc "timezones": a one for you personal trips and several ones for people you frequently communicate with. It is a nice option, but might be too complicated for usage. It may be easier to suspend regular entry and to add custom ones with no requirements related to the code. Anyway it assumes some communication between participants.