From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9568 invoked by alias); 16 Aug 2017 15:16:09 -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: 22832 Received: (qmail 10337 invoked by uid 1010); 16 Aug 2017 15:16:09 -0000 X-Qmail-Scanner-Diagnostics: from mta03.eastlink.ca by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(24.224.136.9):SA:0(-2.6/5.0):. Processed in 1.79703 secs); 16 Aug 2017 15:16:09 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD, SPF_PASS autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_2/jJ3UfJGUjaSmNUXhaw8w)" X-Authority-Analysis: v=2.2 cv=b5/C2pOx c=1 sm=1 tr=0 a=8gj3v1wGPP1N//wMR4mB5g==:117 a=8gj3v1wGPP1N//wMR4mB5g==:17 a=r77TgQKjGQsHNAKrUKIA:9 a=pG6Flhpj-mpQvsGukqwA:9 a=QEXdDO2ut3YA:10 a=pGLkceISAAAA:8 a=_bjfwdAGbWooTOC6WrQA:9 a=7WjXhVuNYaG2wVwU:21 a=_W_S_7VecoQA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 X-EL-IP-NOAUTH: 24.207.98.138 Subject: Re: PATH_DIRS To: linuxtechguy@gmail.com, zsh Users References: <1852003c-c07c-dc61-b863-007f0cef9111@eastlink.ca> <95eb4234-b82c-f445-e21f-5fb99d689562@eastlink.ca> From: Ray Andrews Message-id: Date: Wed, 16 Aug 2017 07:45:59 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 In-reply-to: Content-language: en-CA --Boundary_(ID_2/jJ3UfJGUjaSmNUXhaw8w) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On 15/08/17 07:30 AM, Jim wrote: > Hi Ray, > Try the following to understand what PATH_DIRS can do: > > mkdir ../System/Subdir > mv ../System/somescript ../System/Subdir > unsetopt pathdirs > . Subdir/somescript # script should not run > setopt pathdirs > . Subdir/somescript # should see output from script > > I believe from reading the man page, this is what PATH_DIRS is > intended to do. As Bart said, it *uses* PATH. If you +x somescript > you can just type: > > Subdir/somescript > > At least this is how I interpreted what PATH_DIRS, as defined in the man > page, does. "Perform a path search even on command names with > slashes in them." Maybe it should say, "In addition to the normal path > search, preform a path search on command names with slashes in them." > Maybe I'm missing some other case use. > > Hope this helps. > > Jim Hugely, thanks Jim. The doc frankly baffled me, now I get it, it adds subdirectories of the path to the (effective) path. Why not just say that? Seemed to be talking about slashes as parts of filenames or some such voodoo. Now Bart's "uses PATH" is understandable. Darkest just before dawn! --Boundary_(ID_2/jJ3UfJGUjaSmNUXhaw8w)--