From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-return-43740-ml=inbox.vuxu.org@zsh.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 9e2ed685 for ; Sun, 28 Oct 2018 21:21:07 +0000 (UTC) Received: (qmail 9223 invoked by alias); 28 Oct 2018 21:20:57 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 43740 Received: (qmail 2926 invoked by uid 1010); 28 Oct 2018 21:20:57 -0000 X-Qmail-Scanner-Diagnostics: from mail-lj1-f178.google.com 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(209.85.208.178):SA:0(-1.9/5.0):. Processed in 1.126577 secs); 28 Oct 2018 21:20:57 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Dwv5fudYhLo+p/AhUk4dN/Mn+R9BGueMj7UiQ2k6q/c=; b=XMWSSbHJ+p+bIWTMEPf+89eGUNhXMWhd5ScIv64obtUPTsNmm1rO3gosoYFij3llru iTIaLfg4+Z5GgPQ01BA05hjOVxkBsGpvdp3xxopYwc8M3eN6MMNHD1Ti56+kUCkYFTKi xf28q36AGt9CgLtWwx+IKAXAN9uEW3KKvIYP/1U/9pQ421M1jBCGWTsMTO2VXClO2No7 osduPfx2SZkLVa0X+642DIKcAoM2tS1yCPmQgfMGIum6EZEgkqNQEX9xJ1OdRhu47bS8 ZoqFGrFbAFqOrOWUA+wvh9rSFQovfh9vp2Rea4yro0Pj+CK48sJb29ZCOmj0DYzrHQj1 fZag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Dwv5fudYhLo+p/AhUk4dN/Mn+R9BGueMj7UiQ2k6q/c=; b=MKOMgKFP3zbJd0tSBXb5oNtfpHBWElsFmdf2rRCOdZbpQax9aNXUNv4ar2SfWsIo05 tBr6lZY9PmMFOcffi0tlDZd6UZwS8bpR9x1cYfxwgHUV+lX0Yyn1i7OoUVzxQ6cKUYPE nkEtr0BZv56SLlUQpiRodywYxFFi/jHLh8CHywPtDC+BrsjGxRxvS3vF84SvdKaKUxTl cCDVmkEAj20GPEFy4EjUOVS7J1FENb/eGbri0fhOTIpY01Tp+dIKbNXowqvxZfRecW1k q3kzUGMaF9R0wcpqP804smNdd+KhojqzU/W1UUelt0wNT7/o6cvgo+PqQ+AApzch1pK9 ux8g== X-Gm-Message-State: AGRZ1gJ+addgc2tyMXBcLFipRmqNEPvqwaC/nILATrqIJWQKK+VJ3OCJ UMU22gv0fKojwUMJKUcuSRbe7zf+tF0FaNReCOci9GtD X-Google-Smtp-Source: AJdET5fCZnDMo3Ej3FIVFZI8ML5RBRnrvFrR2J9SMjsnZ9XWeBywpjtCep1U7cJmvLr/wQK+pMh7CWU0XycxtQ9WMCc= X-Received: by 2002:a2e:9547:: with SMTP id t7-v6mr7358835ljh.63.1540761652195; Sun, 28 Oct 2018 14:20:52 -0700 (PDT) MIME-Version: 1.0 References: <1BE52C46-161F-412B-A539-4B0EA87A2FCE@dana.is> In-Reply-To: From: Bart Schaefer Date: Sun, 28 Oct 2018 14:20:40 -0700 Message-ID: Subject: Re: Inconsistencies in "-quoting and @-splitting, could someone elaborate? To: Sebastian Gniazdowski Cc: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Oct 28, 2018 at 8:41 AM Sebastian Gniazdowski wrote: > > (one could think that if a flag takes the responsibility for > splitting in string-context ("-quoted), then that it will mimic the > first tool to do that, the @) Just to beat this entirely to death, you are wrong because that is NOT WHAT @ DOES. > 2.description) if ${(@)array} makes single-element quoted array back > an array again, then shouldn't @ acting on single-element data (Bart > said it's not array) returned by (z)/(s::) also make it an array > again? We could have done that instead of using (A), but it would have broken historical behavior, so we did not. > 3.description) Basically, the general method of Zshell to obtain > scalars with no splits =E2=80=93 double-quoting =E2=80=93 isn't followed = by (z) and > (s::) flags. Also explained in my first message. Implicit joining occurs before explicit splitting. > The manuals often elaborate about some situations This is spelled out in painful detail in the "Rules" subsection.