From: James Jong <ribonucleico@gmail.com>
To: "Lawrence Velázquez" <larryv@macports.org>
Cc: zsh-users@zsh.org
Subject: Re: Latest stable release of zsh triggers the addition of paths to $PATH
Date: Wed, 13 Mar 2013 16:43:20 -0400 [thread overview]
Message-ID: <CAD4ivxUE16UARmv-TuHT+zqSXWU9Nb9bSXy0ZVZdM6O6P+EjHA@mail.gmail.com> (raw)
In-Reply-To: <7054F6AC-DD66-4174-A199-D30DBF5E5E4A@macports.org>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Thanks yes. There are lots of /etc/z* files and some of them have stuff in
them, so that seems to be the problem. More specifically:
The file /etc/zprofile sources /etc/profile which has stuff in it
The file /etc/zshrc has the following:
if [ "x$SHLVL" != "x1" ]; then
for i in /etc/profile.d/*.sh; do
if [ -r "$i" ]; then
. $i
fi
done
unset i
fi
At this point I have some questions:
1) What doest the if statement above test?
2) When I run a zsh script, how can I prevent it from running /etc/zshrc?
3) When I switch to zsh from tcsh on an interactive shell using exec zsh
-l, how I can I prevent it from running /etc/zprofile?
Thanks again for all your help,
James
On Tue, Mar 12, 2013 at 8:20 PM, Lawrence Velázquez <larryv@macports.org>wrote:
> On Mar 12, 2013, at 6:26 PM, James Jong <ribonucleico@gmail.com> wrote:
>
> > Thanks. I just checked and /etc/zshenv is empty (it only has a few
> automatically-generated comments explaining what it is for).
>
> Are there any other /etc/z* files?
>
> vq
next prev parent reply other threads:[~2013-03-13 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 22:08 James Jong
2013-03-12 22:18 ` Lawrence Velázquez
2013-03-12 22:26 ` James Jong
2013-03-13 0:20 ` Lawrence Velázquez
2013-03-13 20:43 ` James Jong [this message]
2013-03-13 20:57 ` Greg Klanderman
2013-03-14 13:40 ` James Jong
2013-03-12 22:19 ` Nikolai Weibull
2013-03-13 0:17 ` Phil Pennock
2013-03-13 0:20 ` 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=CAD4ivxUE16UARmv-TuHT+zqSXWU9Nb9bSXy0ZVZdM6O6P+EjHA@mail.gmail.com \
--to=ribonucleico@gmail.com \
--cc=larryv@macports.org \
--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).