From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9810 invoked by alias); 13 Mar 2013 00:34:53 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17692 Received: (qmail 11714 invoked from network); 13 Mar 2013 00:34:49 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL, DKIM_SIGNED,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,UNPARSEABLE_RELAY autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at spodhuis.org does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201210; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=clGj0gFm5OMH+c8DczofhG6JXNlTzOnyx/Wlj6AJhs0=; b=Jm7woMYfiBupcX+nliuuHkaVSCm4HRvxtONpAuJbg0AWucoYUvEL6HVVaUCn85O88OnGh60KE2ZK9yk2RyrycmFh0NxwEARE0KNdkr/geAxlzT6lOhVACZxPpO5Xl2tGdGuqhtI4BPgavz0qWbpB43m9TV3FMFXQzIBm4gmYM5c=; Date: Tue, 12 Mar 2013 20:17:38 -0400 From: Phil Pennock To: James Jong Cc: zsh-users@zsh.org Subject: Re: Latest stable release of zsh triggers the addition of paths to $PATH Message-ID: <20130313001738.GA23091@redoubt.spodhuis.org> Mail-Followup-To: James Jong , zsh-users@zsh.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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