From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Bart Schaefer" <schaefer@brasslantern.com>,
"Zach Riggle" <zachriggle@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Why is path not a -aUT type?
Date: Tue, 31 May 2022 13:44:28 -0400 [thread overview]
Message-ID: <2889348c-ca0c-4425-85c0-846a0c4f2bba@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7bGk4FytRXDW_paf15j78B9Ds79AXOZ7bpkAE5JfQ_OBw@mail.gmail.com>
On Tue, May 31, 2022, at 1:22 PM, Bart Schaefer wrote:
> On Tue, May 31, 2022 at 4:16 AM Zach Riggle <zachriggle@gmail.com> wrote:
>>
>> Is there any reason that, by default, we do not
>>
>> typeset -aUT PATH path
>
> The main one is that PATH is imported from the environment and it's
> messy to immediately mung it and push it back there before we've even
> finished the rest of pre-RC-file shell initialization. Further, it's
> not up to us to decide how that value should be passed through to
> child processes when zsh is used as a launcher by/for some other
> application.
It's also presumptuous to assume that all users want this.
I actually stopped deduplicating PATH/path recently because I want
to know when some application or other is trying to modify it behind
my back without having zsh possibly deduplicate the evidence away.
--
vq
next prev parent reply other threads:[~2022-05-31 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 11:16 Zach Riggle
2022-05-31 12:30 ` Andreas Kusalananda Kähäri
2022-05-31 17:22 ` Bart Schaefer
2022-05-31 17:44 ` Lawrence Velázquez [this message]
2023-04-01 0:01 ` Daniel Shahaf
2023-04-02 7:56 ` Daniel Shahaf
2023-04-02 16:00 ` Ray Andrews
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=2889348c-ca0c-4425-85c0-846a0c4f2bba@www.fastmail.com \
--to=larryv@zsh.org \
--cc=schaefer@brasslantern.com \
--cc=zachriggle@gmail.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).