From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-22425-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 16560 invoked by alias); 25 Jan 2017 05:47:27 -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: 22425
Received: (qmail 20702 invoked from network); 25 Jan 2017 05:47:27 -0000
X-Qmail-Scanner-Diagnostics: from mta03.eastlink.ca by f.primenet.com.au (envelope-from <rayandrews@eastlink.ca>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(24.224.136.9):SA:0(-3.9/5.0):. 
 Processed in 0.571168 secs); 25 Jan 2017 05:47:27 -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.9 as permitted sender)
X-Authority-Analysis: v=2.2 cv=ZvqvEJzG c=1 sm=1 tr=0
 a=28Ntk8jg+Dho8ABWn/CRtA==:117 a=28Ntk8jg+Dho8ABWn/CRtA==:17 a=N659UExz7-8A:10
 a=fLDzn3rP1jY8jQBANrQA: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>
 <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>
 <alpine.LRH.2.00.1701242042580.4560@toltec.zanshin.com>
From: Ray Andrews <rayandrews@eastlink.ca>
Message-id: <5268a472-f5d0-9678-ab8f-44c2b0067163@eastlink.ca>
Date: Tue, 24 Jan 2017 21:47:23 -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: <alpine.LRH.2.00.1701242042580.4560@toltec.zanshin.com>
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 7bit

On 24/01/17 08:56 PM, Bart Schaefer wrote:
> 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.).
>
Sure.  If only one couldlearn this stuff other than the hard way.  I'd 
sure like to have a conversation with myself of three years ago and tell 
me what I know now.  I think back to expecting zsh to be something like 
C, now I understand that they couldn't be more different and why that is.