‐‐‐ Original Message ‐‐‐
On Saturday, August 28, 2021 4:49 PM, Robert Elz wrote:
> Date:Sat, 28 Aug 2021 15:26:28 +
> From: hancooper
>
> Message-ID:
>
>
>
> | Would the code break if I use shortopts="Vuhv:s" (allows g
‐‐‐ Original Message ‐‐‐
On Friday, August 27, 2021 8:52 PM, Robert Elz wrote:
> Date:Fri, 27 Aug 2021 17:20:39 +
> From:nigelberlinguer
>
> Message-ID:
>
>
>
> | It should be noted though, that the POSIX requirement by "Guideline 7"
> | is not guided b
"
> 1629544775 183030
> $ echo "${now%[![:digit:]]}" "${now#[![:digit:]]}"
> 1629544775 183030
>
> On Fri, Aug 20, 2021 at 10:30 PM hancooper via Bug reports for the GNU
> Bourne Again SHell bug-bash@gnu.org wrote:
>
> > I am using EPOCHREALTIME and the
‐‐‐ Original Message ‐‐‐
On Friday, August 20, 2021 8:00 PM, Kerin Millar wrote:
> On Fri, 20 Aug 2021 19:28:25 +
> hancooper via Bug reports for the GNU Bourne Again SHell bug-bash@gnu.org
> wrote:
>
> > I am using EPOCHREALTIME and then computing the c
I am using EPOCHREALTIME and then computing the corresponding human readable
form, that can handle
changes in locale
now=$EPOCHREALTIME
printf -v second '%(%S)T.%s' "${now%[^[:digit:]]*}" "${now#*[^[:digit:]]}"
printf -v minute '%(%M)T' "${now%[^[:digit:]]*}"
printf -v hour '%(%H)T' "${now%[^[:di
‐‐‐ Original Message ‐‐‐
On Thursday, August 19, 2021 12:58 PM, Léa Gris wrote:
> Le 19/08/2021 à 14:43, hancooper via Bug reports for the GNU Bourne
> Again SHell écrivait :
>
> > Have been using $EPOCHREALTIME but can see that the output is as follows.
> > 1629
Have been using $EPOCHREALTIME but can see that the output is as follows.
1629376497,853634
The utilisation of tho comma `,` is very inconvenient for those who want to do
time
computations. A change towards a period `.` would be the proper way to display
the
variable.
Furthermore, one gets nan
