From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13662 invoked by alias); 24 Jan 2017 22:31:39 -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: 22420 Received: (qmail 12574 invoked from network); 24 Jan 2017 22:31:39 -0000 X-Qmail-Scanner-Diagnostics: from mercury.zanshin.com 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(64.84.47.142):SA:0(-0.0/5.0):. Processed in 0.952943 secs); 24 Jan 2017 22:31:39 -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.0 required=5.0 tests=SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at ipost.com designates 64.84.47.142 as permitted sender) Date: Tue, 24 Jan 2017 14:31:02 -0800 (PST) From: Bart Schaefer Reply-To: Bart Schaefer To: zsh-users@zsh.org Subject: Re: Avoiding the zshells intelligence...in one case In-Reply-To: Message-ID: References: <20170122080153.GA5042@solfire> <213742a3-d208-973d-3b86-1ac29b9d96dd@eastlink.ca> <2f69cfec-46e2-1a93-101d-fb0579d0637f@gmx.com> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) X-Face: "f/X=UCVgd*^c>+x(gMq0at?e:woX+;'snkkRzc3SX<0AZ (/PS4.M2hzGS9X:Qj]at_H/%a9K}:-eS<"v_7vX84PG9Bf Zpb`wI!I4geY=or+nWq`3CX`oq&TJR;g^ps|7(MH?jh;bs %vHJfCh5>a*6Re5m|Bidja\\o]>n\A)ib1:yX*T`zR(*h~ %tOw<~!D9{e6h!8M2:d8G2@K>y^1I_Vdy\d\MYe]z7c MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 24 Jan 2017, Ray Andrews wrote: > Sure, but if we have any chains -- one command calling another -- we end > up loosing the quotes as things are passed along. That's not true UNLESS you've either used a poorly constructed alias (which is not really "one command calling another") or you have explicitly removed quoting with "eval" or a parameter expansion flag. Once a word is properly quoted inside a parameter value, even a positional parameter, it remains properly quoted until you mess with it somehow (which might include having SH_WORD_SPLIT set, but that's why that's not set by default). > > an ampersand; & isn't an expansion, just other shell syntax > > And that's just what I'm saying -- it would be nice to have some sort of > bomb-proof zero expansion ability. You're missing the point. You can't "bomb-proof" syntactic tokens like "&" without fundamentally changing the language. It's like asking a C compiler not to recognize semicolons.