From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10654 invoked by alias); 8 Jan 2015 16:35:57 -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: 34171 Received: (qmail 2847 invoked from network); 8 Jan 2015 16:35:50 -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=T/C1EZ6Q c=1 sm=1 tr=0 a=rhK92a8tbrCHi84BnR0MuQ==:117 a=rhK92a8tbrCHi84BnR0MuQ==:17 a=Hpgzp-inWqAA:10 a=N659UExz7-8A:10 a=q2GGsy2AAAAA:8 a=JwWJYK0x80Tqbv4BrJ8A:9 a=pILNOxqGKmIA:10 Message-id: <54AEB1E3.1020804@eastlink.ca> Date: Thu, 08 Jan 2015 08:35:47 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.3.0 MIME-version: 1.0 To: zsh-workers@zsh.org Subject: Re: [PATCH] Re: Insecure tempfile creation References: <20141222203624.GA24855@tarsus.local2> <141227223029.ZM15959@torch.brasslantern.com> <141227234421.ZM16038@torch.brasslantern.com> <141228004101.ZM28486@torch.brasslantern.com> <20141229004957.GA1737@tarsus.local2> <141228200142.ZM22840@torch.brasslantern.com> <20150107220345.GE1714@tarsus.local2> <20150108064816.GA17816@lorien.comfychair.org> <150108000821.ZM7996@torch.brasslantern.com> <20150108142420.141e5f4b@pwslap01u.europe.root.pri> In-reply-to: <20150108142420.141e5f4b@pwslap01u.europe.root.pri> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 01/08/2015 06:24 AM, Peter Stephenson wrote: > On Thu, 8 Jan 2015 00:08:21 -0800 > Bart Schaefer wrote: >> Fortunately, we have the zsh/files module which provides a buitin "ln" >> with well-defined semantics. Hopefully that's good enough. > It's a little bit tangential, but it's always bothered me that the only > option we have for module builtins of this kind is to import the into > the command namespace under the standard name, trashing the use of the > system-standard utility your code may elsewhere depend on That is, you > can use "command ln" if you need to, but the point is in the majority of > existing code you would never have bothered to do that. > > We made special arrangements for (z)stat but that really doesn't scale > well. > > Apart from (z)stat, most of the builtins that look like standard utilies > are only there for special cases, e.g. for some reason you can't get to > the file system where they live, in which case there's no real problem. > But for uses like this there potentially is. What an interesting thought. Reading, as I just did about some 'other' 'ln' I: '$ whence ln' and what I get is '/bin/ln' ... and I shrug my shoulders and move on. So are you saying that zsh has an internal 'ln'? If so how can I learn about it? I know we have uniquely named zsh functions, but I have no idea about any that share standard names. man zshbuiltins doesn't mention any 'ln'. What am I missing?