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 24-hour clock by default, meaning it cannot force them do 12-hour clock when requested, so the proposal feels like a one-way road. Anyways, it is like you didn't read my reply, I was saying: I don't think we want to do your proposal. Svyatoslav Mishyn <j...@juef.net> wrote: > (Wed, 23 Feb 09:13) Theo de Raadt: > > We do not have a firm rule that all programs must use 24-hour clock, > > and I don't think we should create such a rule either. > > OK, how about then before printing a date to check T_FMT_AMPM[0]? > But if it were added to all code where approriate, then it would change > standard behavior to some programs which currently display in 24-hour > format... > so again no. > > As like in DragonflyBSD/FreeBSD: > https://gitweb.dragonflybsd.org/dragonfly.git/blob/022bb0a9ed6967bc18e421ed074f5727e49314e0:/usr.bin/w/w.c#l133 > https://cgit.freebsd.org/src/tree/usr.bin/w/w.c?h=2d3725d62acbaca2fe84d43e8fd32ae9fb9a915b#n151 > > [0]: > https://pubs.opengroup.org/onlinepubs/9699919799.2008edition/basedefs/V1_chap07.html >
