From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27682 invoked by alias); 28 Sep 2015 22:04:58 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 36687 Received: (qmail 4208 invoked from network); 28 Sep 2015 22:04:57 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=KC+SolVHKiHU2Vi0LtrOwEcUe49Tj3q1vaZXbc/OtrU=; b=iB6QarWIvEUuML13zwQHKfA7vQ4pe7rOyWga0cxuu/cDfQ0GEyHQOUXXtd3H5K6Zeb 0gkYBZ48nOoXey+v4YqIbEvXDuUsWnJoK6sHfJOizjlG9yWRKg/aqPtcXAW/oeW/pznY TETJII5tqbJAfx08yEx09DN0pCHFCmRYpZ+bxZWGpy0YWiZKZNXgJOIhps15MXYEKOzU gFCvBClBnqg0Hr/ET2h0c8lzy24Q4eHvo4ZdMui0P/LJNFwMZ8HigxG51D2JhMaYueC8 f/71naV5mQieAm+nl22IqlaN66m8PmSvtvzwWV79h1UysKoi8RHqCuOjhXNXc6UR/t7/ EbTA== X-Gm-Message-State: ALoCoQk5LE+GCetuIVjF8SyhkW+LvpE9+gzirdfeoSPsf73FApS2woLIH1bIMmMVfnF4MZhHlRRC X-Received: by 10.60.176.37 with SMTP id cf5mr12180590oec.19.1443477895357; Mon, 28 Sep 2015 15:04:55 -0700 (PDT) From: Bart Schaefer Message-Id: <150928150451.ZM15475@torch.brasslantern.com> Date: Mon, 28 Sep 2015 15:04:51 -0700 In-Reply-To: <20150928181315.GB4921@tarsus.local2> Comments: In reply to Daniel Shahaf "Re: bug with $PWD in /" (Sep 28, 6:13pm) References: <20150916162630.GA6436@chaz.gmail.com> <150919110800.ZM22888@torch.brasslantern.com> <20150919192850.GB6421@chaz.gmail.com> <150919134740.ZM23592@torch.brasslantern.com> <20150928181315.GB4921@tarsus.local2> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh hackers list Subject: Re: bug with $PWD in / MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 28, 6:13pm, Daniel Shahaf wrote: } Subject: Re: bug with $PWD in / } } Looking at the sole caller of ispwd(), setupvals(), it sometimes } initializes $PWD from getenv("HOME"). Is something like this needed, } then? What you're asking is: Are we required to accept PWD instead of HOME when they both refer to the current directory but PWD gets there via a symlink path? I think the answer is "no" but I also don't think your patch did what you intend. We already ignore both $HOME and $PWD when EMULATE_ZSH (and the current directory actually is the home directory).