Re: date(1) in stretch and buster
- Date: Mon, 8 Apr 2019 13:23:26 -0400
- From: Cindy Sue Causey <butterflybytes@xxxxxxxxx>
- Subject: Re: date(1) in stretch and buster
On 4/8/19, Étienne Mollier <etienne.mollier@xxxxxxxxxx> wrote:
> On 4/8/19 5:26 PM, Reco wrote:
>> Dear list,
>> the following thing got my attention recently:
>> stretch$ TZ=UTC date
>> Mon Apr 8 15:22:02 UTC 2019
>> buster$ TZ=UTC date
>> Mon 08 Apr 2019 03:22:04 PM UTC
>> It's not that I depend on certain date format in scripts, but I got used
>> to this 24-hour time format after all these years. And yes, I can commit
>> into my memory that I can achieve old behaviour with "date -R" or
>> "busybox date".
>> My question is - can anyone suggest me appropriate LC_TIME setting that
>> can show buster's date in stretch's format?
> Good Day Reco,
> >From Sid:
> $ LC_TIME=en_US.UTF-8 TZ=UTC date
> Mon 08 Apr 2019 05:07:44 PM UTC
> $ LC_TIME=C.UTF-8 TZ=UTC date
> Mon Apr 8 17:08:59 UTC 2019
> If you speak C, it looks like a good bet.
My half-penny's worth is that my reaction was, "Now that you said
that, I'd like mine to be in the '2009.04.08' format."
Which then brought to mind that at least some file managers, e.g.
Thunar for sure, allow us the option to alter the date format for e.g.
the "Date Modified" column.
That means those variables are buried in that package's code
somewhere. Somewhere at some point, I encountered a package that
offered a rather large selection that covers a lot more tastes in date
formatting solutions, but I can't remember where I saw that..
Found this over at Tecmint:
locale -k LC_TIME
Very coo AND further implies *WHAT ELSE can that little puppy do*, but
my brain's already cognitively sundowning so am passing the baton on
for someone who can run that full distance. :)
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *