From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
Clinton Bunch <cdb_zsh@zentaur.org>,
zsh-users@zsh.org
Subject: Re: set temporary environment variables for builtins
Date: Sun, 17 Dec 2023 08:54:17 +0100 [thread overview]
Message-ID: <CAN=4vMoTBpFV=cO243yurEC=7x2XqEO+wmJBRcMMEvG3TxhyLQ@mail.gmail.com> (raw)
In-Reply-To: <17da96e7-6bac-446f-9d7a-5e7ff408106c@app.fastmail.com>
On Sun, Dec 17, 2023 at 1:27 AM Lawrence Velázquez <larryv@zsh.org> wrote:
>
> On Sat, Dec 16, 2023, at 3:27 PM, Bart Schaefer wrote:
> > On Sat, Dec 16, 2023 at 12:22 PM Lawrence Velázquez <larryv@zsh.org> wrote:
> >>
> >> It does work, in general.
> >
> > Well, no, it doesn't. It works for parameters that zsh separately
> > considers to be "special", which includes all the LC_* variants. TZ
> > is not special.
>
> Huh, this is very surprising to me. I guess I never noticed because
> almost all the variables that can influence builtins (e.g., CDPATH,
> LC_*, OPTIND, etc.) are special.
I am also surprised by this. It does make sense given the
implementation details but it's not how I expected zsh to behave.
Would it make sense to make all parameters that affect builtins
special? Are there parameters other than TZ that affect builtins but
aren't already special?
Roman.
prev parent reply other threads:[~2023-12-17 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 17:59 Clinton Bunch
2023-12-16 18:53 ` Lawrence Velázquez
2023-12-16 19:48 ` Clinton Bunch
2023-12-16 20:20 ` Bart Schaefer
2023-12-16 20:21 ` Lawrence Velázquez
2023-12-16 20:27 ` Bart Schaefer
2023-12-16 20:31 ` Roman Perepelitsa
2023-12-16 20:35 ` Bart Schaefer
2023-12-16 23:53 ` Mikael Magnusson
2023-12-17 0:26 ` Lawrence Velázquez
2023-12-17 7:54 ` Roman Perepelitsa [this message]
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='CAN=4vMoTBpFV=cO243yurEC=7x2XqEO+wmJBRcMMEvG3TxhyLQ@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=cdb_zsh@zentaur.org \
--cc=larryv@zsh.org \
--cc=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).