zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: print builtin preceded by parameter assignment
Date: Thu, 11 Apr 2019 13:58:36 -0700	[thread overview]
Message-ID: <CAH+w=7a7WfCX7nRRN7rOk8ZMpOSRV5Tt0a9CHtYJhikhffrmLg@mail.gmail.com> (raw)
In-Reply-To: <20190411104040.GA29775@cventin.lip.ens-lyon.fr>

On Thu, Apr 11, 2019 at 3:42 AM Vincent Lefevre <vincent@vinc17.net> wrote:
>
> On 2019-04-10 10:25:18 -0700, Bart Schaefer wrote:
> > For what it's worth, Bash seems to (mostly) agree with the zsh
> > interpretation.  If I set HISTTIMEFORMAT to something containing %Z
> > and then run "TZ=UTC history" I get timestamps in the local timezone
>
> Your test seems incorrect.

My bash version is 3.2, so this changed in 4.something.

The actual takeaway here is that TZ has to be pushed into the actual
environ strings, not just set temporarily as a local to the shell, in
order for the system time libraries to apply it to strftime et al.
Most other variables used by shell builtins would not have this
property.

  reply	other threads:[~2019-04-11 20:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190410125753epcas1p4052249a86c562165e1fe2a485d70e70b@epcas1p4.samsung.com>
2019-04-10 12:55 ` Vincent Lefevre
2019-04-10 13:14   ` Peter Stephenson
2019-04-10 14:11     ` Vincent Lefevre
2019-04-10 14:39       ` Peter Stephenson
2019-04-10 17:25         ` Bart Schaefer
2019-04-11 10:40           ` Vincent Lefevre
2019-04-11 20:58             ` Bart Schaefer [this message]
2019-04-11 21:42               ` Bart Schaefer
2019-04-24 12:31                 ` Vincent Lefevre
2019-04-24 16:00                   ` Bart Schaefer
2019-04-25 19:47                     ` Bart Schaefer
2019-04-11 10:45         ` Vincent Lefevre

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to='CAH+w=7a7WfCX7nRRN7rOk8ZMpOSRV5Tt0a9CHtYJhikhffrmLg@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.vuxu.org/mirror/zsh/

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).