From: Perry Smith <pedz@easesoftware.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Rob Mardin <rmardin@gmail.com>, zsh-users@zsh.org
Subject: Re: Missing .zshenv file in /etc
Date: Wed, 27 May 2020 09:00:39 -0500 [thread overview]
Message-ID: <1536AEE5-7C5F-4EDA-8DF0-AFB780E0850A@easesoftware.com> (raw)
In-Reply-To: <853619536.203578.1590585364556@mail2.virginmedia.com>
I have these files:
-rw-r--r-- 1 root wheel 260 Oct 13 2019 /etc/zshenv
-r--r--r-- 1 root wheel 3094 Feb 29 00:58 /etc/zshrc
-rw-r--r-- 1 root wheel 911 Sep 3 2019 /etc/zshrc_Apple_Terminal
I’m on macOS 10.15.4 and I did a fresh install so I’m pretty sure I have the “stock” configuration.
> On May 27, 2020, at 8:16 AM, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
>
>
>> On 27 May 2020 at 13:58 Rob Mardin <rmardin@gmail.com> wrote:
>> Hello there; I am scratching my head to find how to create .zshenv in /etc
>> folder on Mac OS (Catalina). I thought that this file is automatically
>> created. Could someone help point me to how to autoconfig, ie reinstantiate
>> zsh so that I have the necessary files to start learning zsh scripting.
>
> No idea about Mac OS, but normally that file --- actually /etc/zshenv, no "."
> --- isn't present on most systems, as it would be executed by every
> single instance of zsh that starts on the system. This is generally a bad
> thing unless there's some overriding local reason for that.
>
> It's much more normal to have other /etc/z* files, trying looking for those.
>
> I'm not sure learning zsh scripting form standard system files is a
> particularly great way anyway, but I'm saying that without having actually
> looked at the Mac OS ones. There will be plenty of examples around the web.
>
> pws
next prev parent reply other threads:[~2020-05-27 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 12:58 Rob Mardin
2020-05-27 13:16 ` Peter Stephenson
2020-05-27 14:00 ` Perry Smith [this message]
2020-05-27 14:54 ` TJ Luoma
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=1536AEE5-7C5F-4EDA-8DF0-AFB780E0850A@easesoftware.com \
--to=pedz@easesoftware.com \
--cc=p.w.stephenson@ntlworld.com \
--cc=rmardin@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).