From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19214 invoked by alias); 13 Dec 2017 07:01:10 -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: 23006 Received: (qmail 29596 invoked by uid 1010); 13 Dec 2017 07:01:10 -0000 X-Qmail-Scanner-Diagnostics: from aok120.rev.netart.pl 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(85.128.245.120):SA:0(-1.9/5.0):. Processed in 13.655347 secs); 13 Dec 2017 07:01:10 -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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: psprint@zdharma.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | X-Virus-Scanned: by amavisd-new using ClamAV (14) Date: Wed, 13 Dec 2017 08:00:51 +0100 From: Sebastian Gniazdowski To: Peter Stephenson , Zsh Users Message-ID: In-Reply-To: <20171212150024.13a1e78b@pwslap01u.europe.root.pri> References: <20171212150024.13a1e78b@pwslap01u.europe.root.pri> Subject: Re: Is outer quoting not needed (docs say "redundant")? X-Mailer: Airmail (442) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline On 12 Dec 2017 at 16:00:24, Peter Stephenson (p.stephenson@samsung.com) wrote: > the substitution. So if necessary they will flag up the fact that the > internal expression is double quoted. But because the parameter > substitution in this case is already double quoted, they have no > additional effect. > > There may be a better example to use in the manual: the example here > uses the "@" flag for splitting, which is only meaningful if the outer > quotes are present. But it does have the use of pointing out that > the double quotes are nested --- which might not be obvious, you > might naively think the "${" and "}" were in two different > double-quoted expressions. Yes the example shows this and that's why I'd keep it. Going further, I once had serious doubts about such quotings overlapping. Digged out a code: gitout=( "${(@f)"$( "${gitcmd[@]}" )"}" ) Is it the same? Top-level quotes mark ${gitcmd[@]} as quoted, so splitting, etc. is done regardless of bottom quoting, but each quoting is kept separate and they don't interact when they are parsed? -- Sebastian Gniazdowski psprint /at/ zdharma.org