From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-22423-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 16266 invoked by alias); 25 Jan 2017 04:57:23 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 22423
Received: (qmail 18595 invoked from network); 25 Jan 2017 04:57:23 -0000
X-Qmail-Scanner-Diagnostics: from mercury.zanshin.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, 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 1.369902 secs); 25 Jan 2017 04:57:23 -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 20:56:46 -0800 (PST)
From: Bart Schaefer <schaefer@brasslantern.com>
Reply-To: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: Avoiding the zshells intelligence...in one case
In-Reply-To: <864415b1-bb85-8b61-1f2e-ae811802fafe@eastlink.ca>
Message-ID: <alpine.LRH.2.00.1701242042580.4560@toltec.zanshin.com>
References: <20170122080153.GA5042@solfire> <alpine.LRH.2.00.1701220936420.4560@toltec.zanshin.com> <slrno8aadl.dbe.martin@lounge.imp.fu-berlin.de> <alpine.LRH.2.00.1701221437530.4560@toltec.zanshin.com> <slrno8chmt.58s.martin@lounge.imp.fu-berlin.de>
 <alpine.LRH.2.00.1701231413380.4560@toltec.zanshin.com> <b7b185d5-00d2-863c-e05f-8a8e56181869@eastlink.ca> <ca42009b-6d56-ae6e-9369-02ffd4258a28@gmx.com> <213742a3-d208-973d-3b86-1ac29b9d96dd@eastlink.ca> <2f69cfec-46e2-1a93-101d-fb0579d0637f@gmx.com>
 <ea629daa-2c59-5b41-4318-c73c5d99a54d@eastlink.ca> <alpine.LRH.2.00.1701241424440.4560@toltec.zanshin.com> <864415b1-bb85-8b61-1f2e-ae811802fafe@eastlink.ca>
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:

> On 24/01/17 02:31 PM, Bart Schaefer wrote:
> > 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 ...
>
> God knows.  I've probably zigged to fix my zags on occasion, which is to
> say that I've had to do funny stuff to fix other funny stuff

Probably we're back to the "different levels of quoting" thing here; i.e.,
even if you've successfully protected everything from interpretation by
the shell language parser, you can still encounter another interpretation
done by the command itself, such as backslashes within "print" and "echo".

In nearly all cases those have a control of their own to force literal
use of arguments ("echo -E", "print -r", etc.).