From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.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 4OC8NgxyxmNSYAEAbAwnHQ (envelope-from ) for ; Tue, 17 Jan 2023 11:01:48 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id YICYNgxyxmOuIQEAauVa8A (envelope-from ) for ; Tue, 17 Jan 2023 11:01:48 +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 B016EB94E for ; Tue, 17 Jan 2023 11:01:48 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pHim5-0000oD-8n; Tue, 17 Jan 2023 05:01:01 -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 1pHill-0000Wk-5k for emacs-orgmode@gnu.org; Tue, 17 Jan 2023 05:00:41 -0500 Received: from mail-pf1-x433.google.com ([2607:f8b0:4864:20::433]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pHilf-0001ut-CJ for emacs-orgmode@gnu.org; Tue, 17 Jan 2023 05:00:37 -0500 Received: by mail-pf1-x433.google.com with SMTP id i1so7985304pfk.3 for ; Tue, 17 Jan 2023 02:00:34 -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=8yse5Dtj+47QpBwec8b/hljE4uCJ5BZl5gpuSLnBTsg=; b=hc9AoW9EaTWX9YFd4wDf8dyc7NTyutXOfhwq9Hi1Q+Hi1ol3teCqU3o4hPOwGp0eP3 6sHfLZvM1p7eDcignrkJpUP6zstanmDfWDI2EwPCZSiOdbBnzjA8A56bL0itwfI0NS+u aQmPMApwHb92EOZz9A/HBr2lCQA1DavMAhNnhq6rWO/VjrNzR9XZao+u5ZtLw30lqUl2 HrMDv2XSPlrYyRbV0iYjVLm1o0LRLj2xH3mvVHlvbHisIjBuRX3yUCEIRWcWQp7hRr+v rW0Xoqat0LdNuBwx5nYnbNalsz/kZeJqQdmz6I2D0ER6dewdBymyig220kAh83hmwQQj bGUQ== 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=8yse5Dtj+47QpBwec8b/hljE4uCJ5BZl5gpuSLnBTsg=; b=XpPrQU3/j58Nx2CbbauR/C/yVOR766kEtfOetW2HCCD0W7XntPcI9NUgj9SM2uLGlk SzlNJRqLhKuqN6IkzbnT3yV9pmj0GeE+Rd5xPlWCxcsJnwXjBez91WxOSmNPLU6Gd2ne OAUEqDT+4uSxeiy1MU+LxiHAAnCpDaGHQyHtQ7BN0WRn1Fqs4O1ibFWijUA20CJGkMNN nLzbPV5VpkagboP+FgnfQFE3lEHGxAtSyZ+Q0lC6Zypy3Wp2rbkmNSMd7b3KAraXKwcc erJeD98I/6lVNS78n6kmjsQe9wKs6WiyRW0LBO9VDAjI1aFV35WS2w2MG65jI3HsG06r ydpw== X-Gm-Message-State: AFqh2kpcmUF+hMuNMkxbchbtvqkcWwCJ6gScLz53SpwmrzOPj0pjmGA7 SjPzSYw/V1Wdtm9LcQMi/wKpTJZHjkI= X-Google-Smtp-Source: AMrXdXuTbIIaCc5wpmJb0XkZHzsvjzOHAP19209mqYPPd+2u48aB4Kwzgoin3mPiGlWeyvcUSa1doQ== X-Received: by 2002:a05:6a00:44c5:b0:580:8c2c:d0ad with SMTP id cv5-20020a056a0044c500b005808c2cd0admr2762686pfb.13.1673949633557; Tue, 17 Jan 2023 02:00:33 -0800 (PST) Received: from dingbat (220-235-140-148.dyn.iinet.net.au. [220.235.140.148]) by smtp.gmail.com with ESMTPSA id z26-20020aa79f9a000000b0058da92f7c8dsm3491374pfr.17.2023.01.17.02.00.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Jan 2023 02:00:32 -0800 (PST) Message-ID: <63c671c0.a70a0220.61aa5.56b8@mx.google.com> X-Google-Original-Message-ID: --text follows this line-- 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> User-agent: mu4e 1.9.14; emacs 29.0.60 From: Tim Cross To: Ihor Radchenko Cc: Daryl Manning , rjhorn@alum.mit.edu, emacs-orgmode@gnu.org Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Date: Tue, 17 Jan 2023 20:45:04 +1100 In-reply-to: <87r0vtiks0.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::433; envelope-from=theophilusx@gmail.com; helo=mail-pf1-x433.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-TUID: Ymbj6QbeIQW1 Ihor Radchenko writes: > Tim Cross writes: > >> It also seems that the solution will need some mechanism (possibly on a >> per time stamp basis) for the user to specify what should happen when >> either the time zone has a daylight savings transition, when the >> timezone rules change or when the user's 'default' time zone changes >> because they have changed locations. > > Could you please elaborate here? I have some meetings scheduled in my org files which show up in the agenda. Meeting 1 is a reoccurring meeting which happens every 2 weeks. All of the people in that meting are in the same timezone as I'm in. When we transition into/out of daylight savings time, I don't want the timestamp to change. THe meeting will remain at 3pm. Meeting 2. This is also a reoccuring meeting. However, this meeting is with people from a number of idfferent time zones. When my timezone moves into or out of daylight savings time, I need the meeting time to be updated - moved forward/back 1 hour. Next week, I'm travelling to a different city for work and will be in a different timezone. I need all my meetings to be adjusted except for those I've already booked that are in the timezone I willl be in while I'm away. Finally, I have a few timestamps I use to track some projects and progress on various tasks as well as reports showing actual and estimated effort comparisons as well as managing billing/invoicing. The actual timestamp times are less important than the calculation of durations etc. When durations do cross daylight savings transition points, it is critical that additonal hours are not accidentally added/removed from the duration calculation. Mistakes here could result in me loosing revenue or over charging clients. So, for the first 2 I probably need to somehow flag/indicate that I do or do not want the time adjusted as a result of a daylight savings transition. For the 3rd group, I only want adjustments for timestamps which are not in the 'current' (where I've travelled to) time zone. The final one is really just about ensuring the transitions don't throw out duration calculations accidentally.