From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-19675-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 25591 invoked by alias); 3 Jan 2015 01:08:10 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 19675
Received: (qmail 3134 invoked from network); 3 Jan 2015 01:08:07 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.2
X-Authority-Analysis: v=2.1 cv=X+5rdgje c=1 sm=1 tr=0
 a=HOv8TPlFSS3eFj132gCofQ==:117 a=HOv8TPlFSS3eFj132gCofQ==:17 a=Hpgzp-inWqAA:10
 a=N659UExz7-8A:10 a=imvnpuGrctgakKGbszYA:9 a=pILNOxqGKmIA:10
Message-id: <54A740F3.4040902@eastlink.ca>
Date: Fri, 02 Jan 2015 17:08:03 -0800
From: Ray Andrews <rayandrews@eastlink.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.3.0
MIME-version: 1.0
To: zsh-users@zsh.org
Subject: Re: symlink chain.
References: <549E3A7B.9010209@eastlink.ca>
 <20150102170307.7d2e644a@ntlworld.com> <54A6E6B1.6070201@eastlink.ca>
 <20150102212422.3a761af5@ntlworld.com> <54A7136C.1060102@eastlink.ca>
 <20150102222140.1303a633@ntlworld.com> <54A72CEF.9090102@eastlink.ca>
In-reply-to: <54A72CEF.9090102@eastlink.ca>
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 7bit

On 01/02/2015 03:42 PM, Ray Andrews wrote:

>
> I put that patch in by hand and it sorts out the  -sa issue, alas:
>
>      $ whence -asm "/usr/bin/zsh"
>      (nothing)
>
Needless to say, I have no idea if this is sound, however:

     /* With -m option -- treat arguments as a glob patterns */
//    if (OPT_ISSET(ops,'m')) {
     if (OPT_ISSET(ops,'m') && **argv != '/' ) {

... seems to work.  I'm just aping what Peter did, of course.  Even when 
one has narrowed down a 'search' to a single file, the command should 
not break.  In that case the command is not so much 'finding' as it is 
informing.

     $ find /etc/fstab
     /etc/fstab

... sure, it's a bit pointless to 'find' an exactly specified file, but 
the command still works, and it confirms that the thing exists. With 
Peter's -S switch one might 'whence' a specific file just to see the 
pointer chain expand.  And the other switches should not break it, even 
if they aren't really doing anything.