From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id WF9IAI0ow2M+8QAAbAwnHQ (envelope-from ) for ; Sat, 14 Jan 2023 23:11:25 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id oBAAO4wow2ODSgAAG6o9tA (envelope-from ) for ; Sat, 14 Jan 2023 23:11:24 +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 A2B893F08D for ; Sat, 14 Jan 2023 23:11:24 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pGojP-0005lS-1Q; Sat, 14 Jan 2023 17:10:31 -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 1pGojE-0005l8-SV for emacs-orgmode@gnu.org; Sat, 14 Jan 2023 17:10:22 -0500 Received: from mail-pf1-x42e.google.com ([2607:f8b0:4864:20::42e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pGojC-0001EJ-Gj for emacs-orgmode@gnu.org; Sat, 14 Jan 2023 17:10:20 -0500 Received: by mail-pf1-x42e.google.com with SMTP id i1so3462043pfk.3 for ; Sat, 14 Jan 2023 14:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:date:subject:cc:to:from:user-agent :references:message-id:from:to:cc:subject:date:message-id:reply-to; bh=eHJ0XVBbOt2hqcn040EQBvPTC5r/0odR9MF5YGuGviw=; b=N9Wo5BpiW6wSfR/EbHMgzu8EBc7XzKh+K+dFKShz93HtzrGmnSTc8s4ZdPJH3s+Slk DZ7u2L1EjwCi4iHFy8+gtco07bE2ZLAG2eXcw+3tlkID1lV+siSuqjWnRfqTJVSBwzQm q7dGbllMaJIDU43kEaGiUecK9a0ZGO1E9iNZjU2pcgVZySz3Y0na1Ek5PlMGNVAgYQxU iw2Bfkduj7GHp+6amftqDJ8xsYJl9MeqKcCIYthx3NSqbK0HoPI61JaZkaNSCu7g9/Rt UvnbKSKDOYg6IzICbcrim3F4/b89VsbStAHm8K6ajJ/IN3/Da+fxpTtBxw9CUbKhMmQ4 1ZaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:in-reply-to:date:subject:cc:to:from:user-agent :references:message-id:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=eHJ0XVBbOt2hqcn040EQBvPTC5r/0odR9MF5YGuGviw=; b=ddOUA+wBmM8EXVZ/8n1r4sFNV4Yld0peDGVQn2gQjlo5wr0oBpO9A5Y3YSFBmMRFvV xjOG1SBLUDWHJSF9s92K6fnjJfSOHUxWRuFsAY9F0H8VYM3uesgcAPLVZkZaFCHo9vNy oIaFDFfYBylituR8lnW6siHAZtnphT7NczxBo/A3flrprhSDlOlVAdlpM7Ffu+57do9S LhJtBp8B0f6KXv4/0T0hdzceCQHM+qnFRB2o+ZTgj6nKG6hswV13rVNwrF009zhFcZis hxUxAoRdxmRa04OaY4tpdTKb/VXdzFQFskp5IC4R5bWPISVq8ls3lgI8aoLrY9PS7FTJ 4AQw== X-Gm-Message-State: AFqh2kp1wMgpGxHL+8eHFodgK5RPumbIMAzLbLK4xLuZ2YKW/cc0BsCY oODL6+SbQBUwd7o76WbGWFds31ngH4k= X-Google-Smtp-Source: AMrXdXu5Gg2KBj0t5WNUB1A4w9xmDBhRCbPBWzg5mG3mLXANF0TjNK3brFrhPnXb8N4sFs2S1jsvsA== X-Received: by 2002:a05:6a00:1c8c:b0:58b:9047:31e2 with SMTP id y12-20020a056a001c8c00b0058b904731e2mr9828732pfw.31.1673734216635; Sat, 14 Jan 2023 14:10:16 -0800 (PST) Received: from dingbat (220-235-140-148.dyn.iinet.net.au. [220.235.140.148]) by smtp.gmail.com with ESMTPSA id y22-20020a626416000000b0058bc745026csm1562996pfb.97.2023.01.14.14.10.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 14 Jan 2023 14:10:16 -0800 (PST) Message-ID: <63c32848.620a0220.dec52.1f9c@mx.google.com> X-Google-Original-Message-ID: --text follows this line-- References: <63c287ca.a70a0220.4bd14.873b@mx.google.com> <87pmbh1hgx.fsf@localhost> <63c2b8e4.a70a0220.e3b6d.0051@mx.google.com> <87edrxyyeq.fsf@localhost> <87bkn1yx59.fsf@localhost> <87lem582qw.fsf@localhost> User-agent: mu4e 1.9.12; emacs 29.0.60 From: Tim Cross To: Ihor Radchenko Cc: tomas@tuxteam.de, emacs-orgmode@gnu.org Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Date: Sun, 15 Jan 2023 08:52:41 +1100 In-reply-to: <87lem582qw.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::42e; envelope-from=theophilusx@gmail.com; helo=mail-pf1-x42e.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com header.s=20210112 header.b=N9Wo5Bpi; 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=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1673734284; a=rsa-sha256; cv=none; b=X9R3LKxbL2kXYeOgOdYKNI368Uc67o8YEUPBqZVWAYLMn+e4IkOZDdt2h5vpTNpGAvqikj ypU3+wCL1Wnxu2Ed3tmgKFVOyXIqLOcxjFI56vCQbOusCCXcns0i9r/KqieLRO+XZBXOY6 LiOiXVtddVUz0CyplM4sG2Htx5rqQdob+lYeorzpkgS9H0rqtAAkob6b5GwOa1jU/kiTUM o5TrRh98+wc9cHtroIQTlAkYEm6VuThITCraont1IoeclX+moD3BB89ZVTMRdBiXybZVEa 9ZsnF8zrnq79emWCV1xHj+cC/uqB2/bgwtVeI8zwl6S+TV8BT9VMuBuinLnQDA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1673734284; 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=eHJ0XVBbOt2hqcn040EQBvPTC5r/0odR9MF5YGuGviw=; b=uM63HA1pVezf2MoTUqjpy8vs8Yu58wRofFKx9lOUKdqAISTcMuNk4Tfa+rQdEsfX2IHbJ5 j7M0PdgHwZtjKVW/2PYh+fh4NTpU363Dyyab6UUIqmwFGlkj5V9wYPRx+8aoz9CojXu9Yo Kk98qVdssAEJEYu4mG2h20OW5PZIV9e35jZ37j2cMOVp9XK7bHrgK2Q+7X7oLxuh0Z1tK6 TMHWlpgN1e/vsljePyL9kM6R/HwPhQinvpgc+mQ/D+Qc+tsh0gFuGD02yk9zGgMzFcSF2W zT0R8U7uVUABlHgEGDWXPakXnCji0wHCMC1D7NAmFgpqvtGHyW7cz5KkqlmJdA== X-Migadu-Queue-Id: A2B893F08D X-Migadu-Scanner: scn0.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=N9Wo5Bpi; 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=gmail.com X-Migadu-Spam-Score: -8.26 X-Spam-Score: -8.26 X-TUID: yriUjkaevvnk Ihor Radchenko writes: > tomas@tuxteam.de writes: > >>> ... Having an >>> ability to specify time zones manually will already cater needs for a >>> number of users. >> >> Definitely. But the time stamp (with time zone) in itself doesn't >> carry enough context to actually decide that. It's even not that >> easy to wrap one's head around dates that "travel" (the easiest >> example would be perhaps: "9:00 show up at work" -- when DST takes >> effect, it's still 9:00 whatever the local time is). > > This is basically what we have now - conform to "current" system time > zone. We are not going to remove this timestamp style. Just add an > ability to explicitly specify the timestamps if needed. > >> When you have appointments with people in totally diverse time zones, >> perhaps dates tend to be more fixed wrt UTC. > > AFAIK, people don't usually bother. As long as you can map from specific > time zone (applying the currently active summer clock time changes) to > something like seconds from epoch, you can always calculate back to you > preferred time zone. Look at https://www.emacswiki.org/emacs/Usergroups. > They say, for example, "Europe/Berlin", which may be either CET or CEST. > > In any case, selection of time zone for user timestamps is not something > we need to worry about in Org code. Users are to decide. Org might > assist, but I do not see anything meaningful we can do to help with DST. I think I basically agree with the last statement. However, perhaps we need to step back and ask ourselves what it is that people do want which drives this feature request. I doubt it is simply the ability to add TZ information to timestamps. I suspect the underlying motivation here is to have org mode actually use this information in a meaningful way, which essentially means all the complicated stuff I'm concerned about and which you seem to imply we wouldn't manage anyway. To put it another way, we need to clarify what people mean when they request the feature of timestamp support in org-mode datestamps. What does this actually mean? Is it as simple as just being able to specify the timezone (seems relatively easy to implement, but doens't really add much) or is the expectation that once you have time zone information, it will be used to do things like adjust date+time in agenda based on change in locale or change in daylight savings status etc. Clarifying the end goal will likely focus the discussion a lot more. My interpretation, which could well be too extreme, is that people want more than just the ability to add TZ info to their timestamps. They want their agenda to reflect correct meeting/schedule times based on their current locale, which may have changed since the initial timestamp was recorded. They want time duration calculations which are able to handle DS transitions etc, they want their agenda/calendar to adjust in a similar way to how their Google calendar will adjust based on DS transitions.