From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19070 invoked by alias); 24 Jan 2017 06:13:06 -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: 22413 Received: (qmail 8483 invoked from network); 24 Jan 2017 06:13:06 -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.9/5.0):. Processed in 1.682296 secs); 24 Jan 2017 06:13:06 -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.9 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.10 as permitted sender) X-Authority-Analysis: v=2.2 cv=DOfN2GFb c=1 sm=1 tr=0 a=28Ntk8jg+Dho8ABWn/CRtA==:117 a=28Ntk8jg+Dho8ABWn/CRtA==:17 a=N659UExz7-8A:10 a=8qv9nDIIT3uCDl0Z6dMA:9 a=pILNOxqGKmIA:10 X-EL-IP-NOAUTH: 24.207.16.108 Subject: Re: Avoiding the zshells intelligence...in one case To: zsh-users@zsh.org References: <20170122080153.GA5042@solfire> From: Ray Andrews Message-id: <213742a3-d208-973d-3b86-1ac29b9d96dd@eastlink.ca> Date: Mon, 23 Jan 2017 21:42:56 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 MIME-version: 1.0 In-reply-to: Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 23/01/17 06:48 PM, Eric Cook wrote: > > That the point of having single quotes, so nothing within them would be treated syntactically. > This thread is just another plead at being even more lazy, to not have remember to use an > option/syntax to treat a string literally. > Except that that doesn't work with command line arguments nor with things like: $ alias junk='echo $path' $ alias wense='whence -m "$1"' and it seems to me that there's lots of other little exceptions here and there where the quotes end up getting stripped off. Thus the need for 'noglob', and for exactly the same sorts of reasons it would be good to be able to assure literal strings in any situation and do it in such a way that it is spelled out what is going on. As Bart pointed out, the tilde can't be protected even by 'noglob', but 'noexpansionsatall' would give perfect results even on Tuesday and be absolutely frank as to what has been done in exotic situations where simple quoting doesn't work. Why does it have to be difficult? Aren't options like 'noglob' the correct answer for this sort of thing? So why not use the same logic to extend complete protection for strings when needed, as in Meino's problem? Even when there is better syntax, sometimes you just want something to work and the option would not only work but be self-commenting. Or not. Maybe this really is sloppy thinking.