From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22171 invoked by alias); 9 Mar 2018 17:50:52 -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: List-Unsubscribe: X-Seq: 23223 Received: (qmail 19810 invoked by uid 1010); 9 Mar 2018 17:50:52 -0000 X-Qmail-Scanner-Diagnostics: from mta01.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.30):SA:0(-2.6/5.0):. Processed in 11.842737 secs); 09 Mar 2018 17:50:52 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=utf-8; format=flowed X-Authority-Analysis: v=2.3 cv=dfKuI0fe c=1 sm=1 tr=0 a=RnRVsdTsRxS/hkU0yKjOWA==:117 a=RnRVsdTsRxS/hkU0yKjOWA==:17 a=IkcTkHD0fZMA:10 a=rBCfpOwSNtTWhh_3HMUA:9 a=QEXdDO2ut3YA:10 X-EL-IP-NOAUTH: 24.207.101.9 To: Zsh Users From: Ray Andrews Subject: unmatched ' Message-id: <2dcec644-7acb-5916-2858-2301206f1da8@eastlink.ca> Date: Fri, 9 Mar 2018 09:50:35 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 Content-language: en-CA I have a function that lists all directories matching a nesting set of strings: $ c etc systemd system ... the list is culled by matching each string in turn.  It works fine except that: $ c etc (eval):1: unmatched ' ... but that's the one and only directory that throws that error.  I've tested dozens of directories and combinations and all are fine except 'etc'. I suspect this abomination: /etc/DSHR's Blog: Using the official Linux overlayfs_files ... God knows why that's permitted, but I'm thinking that the single quote is doing the obvious thing as far as 'eval' in concerned.  Can I prevent that?  Or, if it must be an error, can I get eval to ignore it somehow? The offending line is this: baz=(`eval print -l $bar $grepstring`) ... I want to sent the output of printing '$bar' after it's been piped through the chain of greps that are built up and saved in the '$grepstring' variable, and save that filtered and colored result in '$baz'.  Apart from the above, it works perfectly.  I'm betting there's a flag ${(flag)bar} that fixes it, i.e. forcing " DSHR's " to be literal.  Otherwise I will excoriate the offending directories.  Work of the Devil.