From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: James Jong <ribonucleico@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Latest stable release of zsh triggers the addition of paths to $PATH
Date: Tue, 12 Mar 2013 20:17:38 -0400 [thread overview]
Message-ID: <20130313001738.GA23091@redoubt.spodhuis.org> (raw)
In-Reply-To: <CAD4ivxXVaur2-yswW1L+TwViEuY8dUij9ZBV9gniJaZyQue-Cg@mail.gmail.com>
On 2013-03-12 at 18:08 -0400, James Jong wrote:
> I first noticed this problem in Zsh 5.0.0, but I have just built Zsh 5.0.2
> from scratch and every time I call exec zsh from another shell (e.g. tcsh).
> My $PATH variable ends up with two additional paths, one pointing to
> Keberos and another one pointing to a version of Qt.
>
> I don't have anything in my .zprofile nor on my .zshrc.
>
> Why are these paths added to $PATH? Any pointers on what I can look at?
tcsh> zsh -x
If you do that, and also capture stderr to a file, and immediately quit,
then you can grep the stderr output for references to PATH or path.
Ignore fpath, module_path, manpath, etc etc.
This should get rid of most of the cruft:
% pcregrep -n '\b(?i)path\b' zsh.trace
Use the line-numbers to find the matches in the full output and trace
back where the lines come from.
-Phil
next prev parent reply other threads:[~2013-03-13 0:34 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
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 [this message]
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=20130313001738.GA23091@redoubt.spodhuis.org \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=ribonucleico@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).