On Sun 17 Dec 2023 at 23:00:37 (+0000), Albretch Mueller wrote: > On 12/17/23, Andy Smith <a...@strugglers.net> wrote: > > All this paranoia, but in computer time you trust? 😀 > > Falsehoods programmers believe about time > > https://gist.github.com/timvisee/fcda9bbdff88d45cc9061606b4b923ca > > and how does my paranoia relate to that wall of itemized statements > which could be reduced to just a few?
I understood the paranoia related to your earlier post, outlining "exposed" and "private" modes and why you require all this date processing to support them. > 2) coreutils date is not quite true to itself when it comes to en- > and decoding its own formatting options Which of its own formatting options does it not support? $ date -Ins | tee /tmp/d-ins 2023-12-17T18:29:38,909648062-06:00 $ date -d "$(cat /tmp/d-ins)" Sun Dec 17 18:29:38 CST 2023 $ date --rfc-email | tee /tmp/d-ema Sun, 17 Dec 2023 18:29:47 -0600 $ date -d "$(cat /tmp/d-ema)" Sun Dec 17 18:29:47 CST 2023 $ date --rfc-3339=ns | tee /tmp/d-rns 2023-12-17 18:29:54.724220949-06:00 $ date -d "$(cat /tmp/d-rns)" Sun Dec 17 18:29:54 CST 2023 $ date | tee /tmp/d-dat Sun Dec 17 18:30:01 CST 2023 $ date -d "$(cat /tmp/d-dat)" Sun Dec 17 18:30:01 CST 2023 $ All correct. When you write dt00=$(date +%Y%m%d%H%M%S) that's /your/ format, not coreutils'. Cheers, David.
