Thanks, Paul,
On 09/07/2024 01:52, Paul Eggert wrote:
On 7/8/24 21:18, Richard Neill wrote:
Also, this is an increasingly common format to see as an input
In shell apps? News to me. I thought it was more of a Java and/or
JavaScript thing. Those languages love ms. POSIX, though, prefers ns.
On 7/8/24 21:18, Richard Neill wrote:
Also, this is an increasingly common format to see as an input
In shell apps? News to me. I thought it was more of a Java and/or
JavaScript thing. Those languages love ms. POSIX, though, prefers ns.
For occasional use one can just use the shell, with no
On 08/07/2024 17:33, Andreas Schwab wrote:
date --date='@1720378861.258' --rfc-3339=ns
Thanks. The problem is that the input string (from elsewhere) is
"1720378861258" i.e. it's "integer ms", not "seconds with a decimal".
Also, this is an increasingly common format to see as an input
Slightly
On Jul 07 2024, Richard Neill wrote:
> I've noticed a lot of systems now return the timestamp in milliseconds
> since the epoch, rather than seconds. This means that e.g.
>
> date --date='@1720378861258'
>
> will do something rather unexpected!
>
> May I suggest that it would be nice if date had
Hello Pádraig,
On 08/07/2024 12:33, Pádraig Brady wrote:
On 07/07/2024 20:46, Richard Neill wrote:
Hello,
I've noticed a lot of systems now return the timestamp in milliseconds
since the epoch, rather than seconds. This means that e.g.
date --date='@1720378861258'
will do something rathe
On 07/07/2024 20:46, Richard Neill wrote:
Hello,
I've noticed a lot of systems now return the timestamp in milliseconds
since the epoch, rather than seconds. This means that e.g.
date --date='@1720378861258'
will do something rather unexpected!
May I suggest that it would be nice if date
