From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29566 invoked by alias); 3 Dec 2016 00:15:28 -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: 22143 Received: (qmail 2706 invoked from network); 3 Dec 2016 00:15:28 -0000 X-Qmail-Scanner-Diagnostics: from mta04.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.10):SA:0(-3.6/5.0):. Processed in 1.50875 secs); 03 Dec 2016 00:15:28 -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=-3.6 required=5.0 tests=RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.eastlink.ca designates 24.224.136.10 as permitted sender) X-Authority-Analysis: v=2.2 cv=HKaBLclv c=1 sm=1 tr=0 a=MRfsBU9oQI9kG0qxcmz51g==:117 a=MRfsBU9oQI9kG0qxcmz51g==:17 a=N659UExz7-8A:10 a=sax-tibLYiIVejZhB3wA:9 a=pILNOxqGKmIA:10 X-EL-IP-NOAUTH: 24.207.105.139 Message-id: <58420E9B.6090501@eastlink.ca> Date: Fri, 02 Dec 2016 16:15:23 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-version: 1.0 To: zsh-users@zsh.org Subject: Re: problem with zmv References: <5840492A.2090304@eastlink.ca> <5841DF8C.8000602@eastlink.ca> <58420592.4040406@eastlink.ca> <161202154727.ZM5584@torch.brasslantern.com> In-reply-to: <161202154727.ZM5584@torch.brasslantern.com> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 12/02/2016 03:47 PM, Bart Schaefer wrote: > On Dec 2, 3:36pm, Ray Andrews wrote: > } > } I just now commented out the 'emulate' line, and it > } seems to run fine. Is that safe? > > It's safe as long as your setopts are "close enough" to the default zsh > configuration plus extendedglob. If you use any of the options such > as globassign or shwordsplit that are going to change certain command > line intepretations, then no, it's not safe. > Thanks Bart. No, I'm not that sort of person. I'll leave it commented for now with a caution and throw myself at autoload again since that seems kosher. BTW, don't I remember something to the effect of changing setopts but only for the duration of a given script? If so, that sounds like a healthy way of doing it.