emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Shironeko <shironeko@tesaguri.club>
Cc: emacs-orgmode@gnu.org
Subject: Re: Idea for handling timezones
Date: Sat, 3 Apr 2021 09:56:08 +0200	[thread overview]
Message-ID: <20210403075608.GA19516@tuxteam.de> (raw)
In-Reply-To: <47bc203d8a8facda27c59c363319ae195d643dba.camel@tesaguri.club>

[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]

On Sat, Apr 03, 2021 at 08:36:06AM +0800, Shironeko wrote:
> On Fri, 2021-04-02 at 13:34 +0200, tomas@tuxteam.de wrote:
> > On Thu, Apr 01, 2021 at 07:40:47AM +0000, shironeko wrote:
> > 
> > Hm. Just a mumbling from the peanut gallery: isn't the timezone a property
> > of the timestamp itself?
> > 
> > Specifying the timezone for the whole file is progress, but imagine the
> > following scenario: I have a big file which is more or less a diary of
> > things which happened, with lots of timestamps thrown in (also LOGBOOK
> > entries).
> > 
> > If I move through timezones, only some of the timestamps are "elsewhere".
> > 
> 
> There are separate hacks for that, see
> https://emacs.stackexchange.com/questions/13463/specify-timezone-in-org-date-format

Thanks for the pointer [1].

Yes, Org is a bit scared to touch time format, and in a way, I do
understand that.

I'm unhappy myself with Org timestamps, but given how conflict-laden
the topic is, I opted for keeping my local hacks and dealing with
some fallout on version changes. Not optimal, but I haven't better
ideas myself currently.

> > Switching "the whole file" to reflect the "current" timezone [...]

> This is why timezones need to be specified in the tz database format, it does
> all the right things and makes sure the converted timestamp corresponds to the
> same instant. 

I don't understand what you mean by "the tz database format" in this
context. What I meant is the '%z' information (e.g. -0400) instead
of (or in addition to) the '%Z' one (e.g. EDT), in the sense of
`format-time-string'.

But perhaps we mean the same.

> > Of course, convincing Org to extend the timestamp format and regexps
> > might be a tough call :-)
> 
> This is exactly the problem I'm trying to avoid.

Yes, I get the "design tension" there. I don't have better ideas.
A greater flexibility in timestamp representation would have seduced
me; a file-global setting... not so much.

Still, I wish you good luck :-)

Cheers

[1] BTW I hate SX. Theycl've come up with yet another of those cookie
   tortures to take revenge on the users for some mild privacy protection
   laws. Of course I don't want any cookies. You @#&$s don't even have
   to ask: you @#*&%$ can infer that from the fact that my browser doesn't
   accept cookies in the first place!  You so-called web programmers
   manage to elicit feelings in me I'm less-than-proud of.

 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2021-04-03  7:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  7:40 Idea for handling timezones shironeko
2021-04-02 11:34 ` tomas
2021-04-03  0:36   ` Shironeko
2021-04-03  7:56     ` tomas [this message]
2021-04-03  8:03       ` shironeko
2021-04-03  8:30         ` tomas
2021-04-03  9:26           ` Shironeko
2021-04-03 11:23             ` Greg Minshall
2021-04-03 15:00               ` Russell Adams
2021-04-03 18:51                 ` Greg Minshall
2021-04-03 20:06                   ` Samuel Wales
2021-04-03 22:47                   ` Tim Cross
2021-04-04  0:51                     ` Tom Gillespie
2021-04-04 16:06                       ` Maxim Nikulin
2021-04-23  1:45                         ` Shironeko
2021-04-23  7:54                           ` tomas
2021-04-03 12:43             ` tomas
2021-04-03 12:47               ` Shironeko
2021-04-03 13:20                 ` Shironeko
2021-04-02 23:37 ` Tim Cross
2021-04-03  0:31   ` Samuel Wales
2021-04-03  0:43   ` Shironeko
2021-04-03  0:53     ` Samuel Wales
  -- strict thread matches above, loose matches on Subject: below --
2021-03-31  2:23 Shironeko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210403075608.GA19516@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=shironeko@tesaguri.club \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).