From: "Lawrence Velázquez" <larryv@macports.org>
To: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
Cc: Nikolai Weibull <now@bitwi.se>, rahul <rahul2012@gmail.com>,
"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: PATH reordered when running zsh inside screen on Mac OS X Mountain Lion and MacPorts
Date: Mon, 28 Jan 2013 17:44:32 -0500 [thread overview]
Message-ID: <E4C864D9-B093-4878-B63E-1DDD2CDDDCA1@macports.org> (raw)
In-Reply-To: <20130128202234.GA2429@redoubt.spodhuis.org>
Hi, I'm the MacPorts maintainer for zsh.
On Jan 28, 2013, at 3:22 PM, Phil Pennock <zsh-workers+phil.pennock@spodhuis.org> wrote:
> 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.
This is precisely my reasoning for not overriding the default setting. It also maintains consistency with the behavior of MacPorts' bash.
vq
next prev parent reply other threads:[~2013-01-28 22:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 9:15 Nikolai Weibull
2013-01-28 9:33 ` rahul
2013-01-28 10:08 ` Nikolai Weibull
2013-01-28 20:22 ` Phil Pennock
2013-01-28 22:44 ` Lawrence Velázquez [this message]
2013-01-29 6:21 ` Lawrence Velázquez
2013-01-29 8:08 ` Lawrence Velázquez
2013-01-29 11:25 ` Nikolai Weibull
2013-01-29 11:24 ` Nikolai Weibull
2013-01-28 9:58 ` Peter Stephenson
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=E4C864D9-B093-4878-B63E-1DDD2CDDDCA1@macports.org \
--to=larryv@macports.org \
--cc=now@bitwi.se \
--cc=rahul2012@gmail.com \
--cc=zsh-users@zsh.org \
--cc=zsh-workers+phil.pennock@spodhuis.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).