From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23027 invoked by alias); 27 Mar 2017 01:45:11 -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: 22623 Received: (qmail 12948 invoked from network); 27 Mar 2017 01:45:11 -0000 X-Qmail-Scanner-Diagnostics: from mta02.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.13):SA:0(-0.7/5.0):. Processed in 0.669085 secs); 27 Mar 2017 01:45:11 -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=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, 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.13 as permitted sender) X-Authority-Analysis: v=2.2 cv=O5RJhF1W c=1 sm=1 tr=0 a=3TxE0GYYoRPvB2ReGANSkw==:117 a=3TxE0GYYoRPvB2ReGANSkw==:17 a=IkcTkHD0fZMA:10 a=t46-5f4NJKHjSjMZhs4A:9 a=QEXdDO2ut3YA:10 X-EL-IP-NOAUTH: 24.207.24.151 Subject: Re: spaces in filenames should be a crime. To: zsh-users@zsh.org References: <0c1b9d89-edd0-a027-e2f1-d01c2d68fa4e@eastlink.ca> <20170326211805.GA8170@fujitsu.shahaf.local2> <9865ba26-3276-4ef1-c24d-fe7dea938d0b@eastlink.ca> From: Ray Andrews Message-id: <764b90a7-cb79-d202-fe69-54176fa1a2f4@eastlink.ca> Date: Sun, 26 Mar 2017 18:45:08 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-version: 1.0 In-reply-to: Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7bit On 26/03/17 06:11 PM, Chris ccb wrote: > It seems to me like, no matter whether you're writing a 4 line script for > home/personal use, or working on some some serious business secure > real-time application to pull some crazy wonder out of thin air, it always > pays to "DTRT" just in the long term time/effort savings alone. Not to > mention the skill/habit forming benefits and potentially reputation that > good code brings along with it. Am I wrong? Heck no. I hope I didn't sound like I was saying otherwise. The thing that bugs the heck out of me is exactly these issues of robustness, there's always another gotcha. It would be fantastic to be able to make things bullet proof right out of the gate, but that seems to be considered an accretion to be learned later on. Mind, anyone who puts newlines in filenames should be burned at the stake, it's sick and twisted. Bart will know how such things were ever permitted in the first place. Mere anarchy was loosed upon the world.