zsh-users
 help / color / mirror / code / Atom feed
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: Tue, 12 Mar 2013 18:26:53 -0400	[thread overview]
Message-ID: <CAD4ivxUg8k906+=kHqny3+fLGoRpGiFNQuzWceY-OXaHv_9k_Q@mail.gmail.com> (raw)
In-Reply-To: <FF30192D-8B2E-432B-B7E9-CEE0D7FACA47@macports.org>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

Thanks. I just checked and /etc/zshenv is empty (it only has a few
automatically-generated comments explaining what it is for).

I'm on a Scientific Linux SL Release 5.1 (Boron).

James







On Tue, Mar 12, 2013 at 6:18 PM, Lawrence Velázquez <larryv@macports.org>wrote:

> On Mar 12, 2013, at 6:08 PM, James Jong <ribonucleico@gmail.com> 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?
>
> What OS are you on? Have you checked whether there are system
> initialization files that could be getting sourced (e.g., /etc/zshenv)?
>
> vq

  reply	other threads:[~2013-03-12 22:52 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 [this message]
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
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='CAD4ivxUg8k906+=kHqny3+fLGoRpGiFNQuzWceY-OXaHv_9k_Q@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).