~soywod/pimalaya#81: 
Improve datetime format

In both the CLI and Neovim plugins I‘m getting the wrong date. A message sent to me this hour reads 17/05/2023 11:36 for which I expect withLC_TIME=en_DK.UTF-8 (ISO 8601) to be 2023-05-17 18:36. I can live with the UTC time as I keep two clocks in my OS‘s bar, but I cannot do little-endian date formats. They cause me too much confusion and do not match user expectations. My other OS locale flags are en_US.UTF-8 which is middle-endian, and while less preferable than big-endian formats, I have an intuition for it.

Status
RESOLVED IMPLEMENTED
Submitter
~toastal
Assigned to
Submitted
1 year, 2 months ago
Updated
1 year, 1 month ago
Labels
2:himalaya 3:cli

~soywod 1 year, 2 months ago

Which version of Himalaya do you use? On the last one, the format looks like 2023-05-17T21:43:28+02:00 which is kind of universal but not so user-friendly. Maybe we could add an option to customize the date format?

~toastal 1 year, 2 months ago

Version is 0.7.1 from Nixpkgs unstable. RFC 3339 to ISO 8601 specifies that you can drop the T which I find to be the bit that brings the most clutter (followed by the time zone offset), but otherwise it is readable. I think in general the user would expect either something universal or tailored to the OS & environment.

~soywod 1 year, 1 month ago

I think in general the user would expect either something universal or tailored to the OS & environment.

I agree with you. I propose the following: the default behaviour is to show the RFC3339 date matching the envelope's timezone, without the T: 2023-05-17 21:43:28+02:00. A more advanced version would be to use the datetime format deducted from the user's environment locale. I would also add also 2 options:

  • One to customize the datetime format

  • One to transform all dates using the user's timezone

Your thoughts?

~toastal 1 year, 1 month ago

That sounds reasonable.

~soywod REPORTED IMPLEMENTED 1 year, 1 month ago

Feature developed on master, it should be released soon.

Register here or Log in to comment, or comment via email.