On 2/23/22 17:58, Laura Smith wrote:
a lot of peole don't do 24 hour clocks well.
For almost everyone outside North America, 24 hour clocks is the *only* thing
they do. A bit like the weird American affection for m/d/y. ;-)
Here in Germany, Bavaria at least, most people are using 12h
co
So you want this command to behave differently in different environments?
Who wants that unpredicabtility? I suspect noone wants that.
Your reference to POSIX is irrelevant because "w" is not a POSIX command.
Furthermore that feature creep in POSIX locales is not done by most
programs which do 2
Svyatoslav Mishyn wrote:
> just wondering why are some programs using 12-hour/24-hour clock format
> by default?
>
> For instance, 12-hour clock format:
> w(1)/uptime(1)
> Should it be fixed?
We do not have a firm rule that all programs must use 24-hour clock,
and I don't think we should creat
On 2/22/22 3:02 PM, Svyatoslav Mishyn wrote:
Hi,
just wondering why are some programs using 12-hour/24-hour clock format
by default?
For instance, 12-hour clock format:
w(1)/uptime(1)
Should it be fixed?
24-hour clock format:
date(1)
ls(1)
stat(1)
systat(1)
top(1)
Well... keep in mind, if t
4 matches
Mail list logo