help / color / mirror / code / Atom feed
From: Jim <linux.tech.guy@gmail.com>
To: zsh <zsh-users@zsh.org>
Subject: Re: Possible inconsistency with use of TZ to change zone output '%Z"
Date: Sat, 8 Jan 2022 09:32:55 -0600	[thread overview]
Message-ID: <CA+rB6GL_yZBQbxesOqL8skz6bx=psXyu=nT62TE61La--jAWsQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZA2Wzw1Kjr1ny1gk+D7-CDWL_36h=pKAAx2P8A5kJRBg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

Unfortunately my searches never found that mail thread. Sorry about that.
I'm sure the print builtin has nothing to do with the results I am getting.

1) DT=${(%):-%D{$Fmt}}
2) zstat -F $Fmt -A A +mtime $F
3) strftime -s DT $Fmt $ET

In each case the results were placed in a parameter then printed if and as

The thread left me somewhat confused, quite a bit to digest. Probably
because I'm
not a "developer" and know enough C to be a danger to myself and those
me. I understand that for a particular system the libraries may differ from
other systems, and once compiled, will "fix" the way it acts(environment
or not). But if parameter expansion is using zsh's strftime shouldn't it
act the
same way as calling strftime directly. My results indicate that they don't.
It seems logical to me that they would. Admittedly I don't know the
internals, so
I'll accept the results and export TZ as needed.

Z-shell is still my all time favorite shell. Never cared for the de facto
linux default.
Sorry for the personal opinion.

Appreciated you taking the time to respond,


On Thu, Jan 6, 2022 at 6:58 PM Bart Schaefer <schaefer@brasslantern.com>

> There's a lengthy discussion of this in the zsh-users thread with
> subject "print builtin preceded by parameter assignment" from April
> 2019.
> The upshot is that some system libraries only use the environment
> strings when interpreting the time zone.

[-- Attachment #2: Type: text/html, Size: 2088 bytes --]

  reply	other threads:[~2022-01-08 15:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  0:39 Jim
2022-01-07  0:58 ` Bart Schaefer
2022-01-08 15:32   ` Jim [this message]
2022-01-12 19:09     ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+rB6GL_yZBQbxesOqL8skz6bx=psXyu=nT62TE61La--jAWsQ@mail.gmail.com' \
    --to=linux.tech.guy@gmail.com \
    --cc=linuxtechguy@gmail.com \
    --cc=zsh-users@zsh.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).