From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.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 kIcKLr64x2N6UwAAbAwnHQ (envelope-from ) for ; Wed, 18 Jan 2023 10:15:42 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id AO39Lb64x2PgVQEA9RJhRA (envelope-from ) for ; Wed, 18 Jan 2023 10:15:42 +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 7C3AB10AA9 for ; Wed, 18 Jan 2023 10:15:42 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pI4XC-0008EG-28; Wed, 18 Jan 2023 04:15:06 -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 1pI4XA-0008E7-Ct for emacs-orgmode@gnu.org; Wed, 18 Jan 2023 04:15:04 -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 1pI4X7-0007dV-Hi for emacs-orgmode@gnu.org; Wed, 18 Jan 2023 04:15:03 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id D10F4240271 for ; Wed, 18 Jan 2023 10:14:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1674033298; bh=fXNvj3thHDnL83B99gdWLtsyK1TvHxDOMwNZUAcYSXc=; h=From:To:Cc:Subject:Date:From; b=MXH7ZrMqrLaLJ/o9PXPAbIikRH2rsE5VFnzOmRLB3sdJqMKwFFhfnpUA6BvBxiAx0 fG/MD4ov2e3RsJKyanHmQ+bWv0jpl4wfjyTg0MHYkzBMQchRRKSSCmIbRsUmBu2g0C uY7pFXQPCOhqn7ctOI0YQG8r0bgoqkdg3BaZR9VG+BIvY1s80WHeziUAkOXczsIOGQ 5UDhe5vd+0faRW+fgMDthpduWXlgL9t5wO65ao/ozzKcC2bIo5PujpYgTDz96E017U mHmdFGzQ6M8J2J/XFQYm1E0DGKjGMZFduKqnhl7NwHF3+JmIhQrmU92JJ0LMy3koZc ZdZ01dIigzSsQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Nxg7y42Kqz9rxN; Wed, 18 Jan 2023 10:14:54 +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: <63c671c0.a70a0220.61aa5.56b8@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> Date: Wed, 18 Jan 2023 09:15:26 +0000 Message-ID: <87fsc88aq9.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=1674033342; a=rsa-sha256; cv=none; b=bWH7fhWdj6TdPy3m6TK+K/zexbdFO4/n+NMJO54nlSQk8mBfwLKcLjCmWu1nQrKWA29HfA tUd1pKsa6qOYlmrBxI8gFbeE3Tc0ZxwhmtrscPJvBfwgRK5w0xkRdh+9gYw/EKa/JAUgrI yk23WNwD2dFLXBHjjtXcTwByIRR8YoWfTk6xkysDgtYmP7LU0swfa1E1X3GOLpQ0tHoWTc Sbj4Whe/k/fnV1oSbhYG/G3Rh4bw6DhBBQFsrzZZfLitVIJMMd4yaMGc/AXNLufbgFK5Nr K3YlKtA1Qzqqpxv3zVlAZSueJJAgFUFsOLbd2C9o/hWMLEtO1aDtiO6k6+FR0Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=MXH7ZrMq; 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=1674033342; 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=FfFa64r3hXtjN3hJgNGaPJt1P6hhZEX6I1uNNxhUXjU=; b=msVLlVXAK32UDuQQ2Y1IiJN7sz8zZPlxnXhZ9S02YDtXBshqYu7MmxWJG86ZukuBkNORgZ R/zo5MFYTUB7GUefBOVB0EINQs94s0d4NQFjW3HeJYDvixwpaijwIXmAHrjtLUL7X3el8A BIUPQeW0Rqz2b72pJSpX/H0rlPc7yDkkXQ7eupRKl4fTZaiV2/2HvTNlBUbSP6tA2+NVoB y1h/oJ0n2XjldFQ45NOkfwxZ8mKnuUUQNmSvNYDq+FzT+qPOm8hJSCUtro9ELj+nOimgrb tLg5uwIbKVym0ephoDQ8xoezImQ4wn/hqBaNbXmqH9P/DmHintCw91uOyMwwKA== X-Spam-Score: -6.38 X-Migadu-Queue-Id: 7C3AB10AA9 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=MXH7ZrMq; 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: -6.38 X-TUID: mMF+FlfJ7iuX Tim Cross writes: >> 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. Specifying the timezone should be good enough. Not specifying will put you at a risk if you travel (you default OS timezone will likely change). > 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. Again, you can just specify the right timezone and let Org translate it to local one when calculating agenda. > 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. If you don't specify the timezone for both old and new meetings, there will be no easy way to deal with this. What you may have to do is: (1) indicate explicit timezone for the meetings in the new place (there will probably be less of them compared to all other meetings); (2) tell Org to use your old time zone as default - it will make the previously scheduled meetings without timezone info use the right time zone. > 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. For the past timestamps, you can either: (1) make Org put UTC offsets when recording clock data; (2) use the idea we discussed about multiple default time zones where you can specify different time zones at different periods of time (before after travel). Does it sound good enough? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at