From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28081 invoked by alias); 28 Jan 2013 20:40:35 -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: 17614 Received: (qmail 20144 invoked from network); 28 Jan 2013 20:40:32 -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-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=wai6xaZPVX7aUustBeJESq0l9ADX+GrizkQoJkZruaY=; b=gCmANuhjrxOFWr8ScfPjCh4hyMgVWE9Yed/f0184SRqi+9f3vfu8+HxEi/z5rbyTNfcaHqh23mKQVJB7fHOn/8wzkncoENutO3kXCxDDBv2xz4PkL/Vsa9L2/dm59gq4PG1uDF94SkyzZ5ntbQyFuuSaWm4KKEJw8Bux6ElbfLw=; Date: Mon, 28 Jan 2013 15:22:34 -0500 From: Phil Pennock To: Nikolai Weibull Cc: rahul , Zsh Users Subject: Re: PATH reordered when running zsh inside screen on Mac OS X Mountain Lion and MacPorts Message-ID: <20130128202234.GA2429@redoubt.spodhuis.org> Mail-Followup-To: Nikolai Weibull , rahul , Zsh Users References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On 2013-01-28 at 11:08 +0100, Nikolai Weibull wrote: > I figured out what the problem was. /etc/zshenv on Mac OS X Mountain > Lion calls a utility called path_helper. I for some reason only > checked /etc/profile. I don’t quite see why MacPort’s zsh checks > /etc/zshenv instead of /opt/local/etc/zshenv (is this hard coded > behavior in Zsh?), No, that's controlled at build configure time by --enable-etcdir and then each individual global config file can also have its path overriden to be different. However, the default is to use /etc/ instead of $prefix/etc -- presumably because config files for shell start-up have always been in /etc. While MacPorts might override it, note that MacOS ships with an older version of zsh, so using two different config files creates issues. There's not a "clearly right" answer, "different config" or "same config" have their pros and cons, but for people trying to minimize the impact on administrators of users switching shells, with files in /etc/ being maintained by a config management system, using the same files for the MacPorts build is IMO least likely to cause backlash that gets the MacPorts version forcibly uninstalled after someone has spent too long debugging an end-user complaint. -Phil