From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-20926-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 17857 invoked by alias); 7 Nov 2015 18:28:40 -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: 20926
Received: (qmail 12391 invoked from network); 7 Nov 2015 18:28:37 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.0
X-Authority-Analysis: v=2.1 cv=X+5rdgje c=1 sm=1 tr=0
 a=Rb7dudWe+J2gL+/7yVpO1Q==:117 a=Rb7dudWe+J2gL+/7yVpO1Q==:17 a=N659UExz7-8A:10
 a=hBnVuJykV7u15h64SfAA:9 a=pILNOxqGKmIA:10
Message-id: <563E42D3.4020104@eastlink.ca>
Date: Sat, 07 Nov 2015 10:28:35 -0800
From: Ray Andrews <rayandrews@eastlink.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-version: 1.0
To: zsh-users@zsh.org
Subject: Re: convolutions
References: <563D5ED5.1070102@eastlink.ca>
 <CAH+w=7bzDJV5bLSr3=bVkAoOm-Yov3DU9w58eqr6daJFCNvw-w@mail.gmail.com>
 <563D9B54.9010604@eastlink.ca> <151107013244.ZM23334@torch.brasslantern.com>
 <563E222C.7040508@eastlink.ca> <151107093353.ZM24145@torch.brasslantern.com>
In-reply-to: <151107093353.ZM24145@torch.brasslantern.com>
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 7bit

On 11/07/2015 09:33 AM, Bart Schaefer wrote:
> So your stress test isn't anywhere near as stressful as you thought.
I have no faith in what I was trying to do, I was just looking for a 
useful method and that was an experiment.  I quite understand that eval 
is far to dangerous to really be useful for what  I was trying to do there.

> There's no shell operation for "expand parameters but not any of the
> other kinds of expansions you know about."  If what you want is some
> kind of text replacement, you should be writing in_file in a text
> processing language (HTML maybe?) rather than in shell syntax.
>
But I should stop whining, cuz I've had a most satisfactory answer:

$ print -R "${(e)$(<junk1)}" >| junk2
$ cat junk2

... just what I want unless there's some gottcha with that, but I doubt 
it. So debating the demerits of a failed idea that I know has failed is 
pointless.  Thanks all.