From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id aOKKKs7EwmMuCAAAbAwnHQ (envelope-from ) for ; Sat, 14 Jan 2023 16:05:50 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id QFdIKs7EwmOgrgAAauVa8A (envelope-from ) for ; Sat, 14 Jan 2023 16:05:50 +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 4B0172C9D8 for ; Sat, 14 Jan 2023 16:05:50 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pGi5g-00031I-Ii; Sat, 14 Jan 2023 10:05:04 -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 1pGi5e-00030r-HZ for emacs-orgmode@gnu.org; Sat, 14 Jan 2023 10:05:02 -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 1pGi5c-0002Pa-AP for emacs-orgmode@gnu.org; Sat, 14 Jan 2023 10:05:02 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 2D32924022A for ; Sat, 14 Jan 2023 16:04:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1673708698; bh=l6gp/Z51COHl+CtBxro0yQGtM6jrEpZTabaoY2vL7n8=; h=From:To:Cc:Subject:Date:From; b=ZEaqSVSiuAdDf8chG92/EijhBH70PVCAV9InyxX2mzAdBOAGeWiAQoQhqlmH+RmFt edKkpKEzWGClKC2Tmh2isx2I3kb6ar6ZJXeRvXLx1jCyWqfSaUUy39zTZePBvM78gB zKVgoKlP5Xu/h9s2LwpBjGBGfBsbn1Z4VCKgMzZdJRxQvPHH5c+22aHXeO0XQEglgS ZWjV1LVA5BHPyErjhtmaVd8OUl9GaCuZCBqTKhA1xPJ61FoYCqy4PAODKHnlBH6seF K3x/czF08r2lvuDgDzIPpGeh8b8bZFwlN/64Uj5EqniKhY4lvBX5WR/u8sa4Vsh4op d8TIrLH9R6aIQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NvM5f4LWWz9rxD; Sat, 14 Jan 2023 16:04:54 +0100 (CET) From: Ihor Radchenko To: tomas@tuxteam.de Cc: emacs-orgmode@gnu.org Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda In-Reply-To: References: <63c287ca.a70a0220.4bd14.873b@mx.google.com> <87pmbh1hgx.fsf@localhost> <63c2b8e4.a70a0220.e3b6d.0051@mx.google.com> <87edrxyyeq.fsf@localhost> Date: Sat, 14 Jan 2023 15:05:22 +0000 Message-ID: <87bkn1yx59.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-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=ZEaqSVSi; 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-Seal: i=1; s=key1; d=yhetil.org; t=1673708750; a=rsa-sha256; cv=none; b=nEYkAHrzdF+wFJ6FSA8h57oLPZB/JTqIgr5UsvernAftkW67UMU0WCe1ntZYOmxVqFH1Y6 W7aL3I0sqqRJdUgxPvQlncxlmZm48cQ4uGHwdRUw8r7vUv9zFMldRiRp5e+Ko33rR37avO BNGVv5brTS9dF3pR6m9m0AvgLaHnI7YHvBWYbOrqkbegRTIIJH8ayuSgc7RzDR9bEMCuz6 WfQ0/cl58EpHcMoagcHEmHlUTD/JsS8QTvzriMyS0km966OYF00RtVZreXwqL3Kk9VwF2F 49KLI65DqLEahHraOOpD3C8SqypxevBWpong/vjK/mA4NuGa2xLh+r5LRGx/Uw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1673708750; 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=qKCfBlrzycpSqued5lRsNsDjyWAAi4lCnMt/vsLU7GQ=; b=ROWeCYWqdnZrnWrOhGTP/tC7ARRh9p9kO8V05ex5iN6UkuCvofYoC2UQ//aJwJBLRovMrr zr2SaGRDkZQ23SCQa3pzxN2sPKbHgP4EeeQaYsd+Z2O+0JhpXCMrnLWdrtEgHVfUXNveEZ nK0SL+RxHG6RMxEGdYLr8EZatezXkd2cwFvirYE5YWlb8PEICE7qg78lx/RbERyNoHbpiD FhGbfGjlWcKYVU+VTS/4QLhWv1MaP3bVMUPVME99stylROeG140SWP07b7YFcafGSMYkL7 5dW8saXYSv9bOc7c6TgpmeCTTrnsnVkaUV/DpIcGb+uVbzOGs2QnMvt4EbRskg== X-Migadu-Queue-Id: 4B0172C9D8 X-Migadu-Scanner: scn0.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=ZEaqSVSi; 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-Migadu-Spam-Score: -10.86 X-Spam-Score: -10.86 X-TUID: y60kN3xgRZOV writes: > Now there's still enough work for the applications to do: presentation, > parsing, disambiguation, if necessary asking the user for help. Someone > mentioned PostgreSQL -- this is a nice example of what can be done beyond > the (comparatively!) boring details of time zone management :-) Do I understand correctly that PostgreSQL insists on using timestamps with time zone info in favour or ordinary timestamps? Exactly to avoid issues with the same timestamp pointing to a different real time from epoch depending on the current OS time zone setting? Thinking more about this, I can see how it can be important for clocking, and similar auto-recorded information. Users may be surprised to record clocking on some task yesterday just to find the clocking data in future upon travelling from Singapore to San Fran. So, when implementing time zones, we may need to take care about adding the time zone info when auto-inserting timestamps. In addition, we may provide some mechanism to set the time zone for: 1. Individual files 2. For all files, including possible time zone transitions over time. What I mean by (2) is when the user travels from, say, Australia to USA, it could be possible to say: Use Australia/Seattle up to certain time and then use USA/Austin. However, the above considerations are just nice-to-haves and should not be a blocker to a more generic time zone support in Org. Having an ability to specify time zones manually will already cater needs for a number of users. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at