From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8732 invoked by alias); 8 Sep 2012 05:38:43 -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: X-Seq: 17235 Received: (qmail 6884 invoked from network); 8 Sep 2012 05:38:32 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <120907223804.ZM22838@torch.brasslantern.com> Date: Fri, 07 Sep 2012 22:38:04 -0700 In-reply-to: Comments: In reply to Sebastian Stark "Re: double quoted expansion question" (Sep 7, 5:43pm) References: <29236168-55B5-4555-9ACA-B1D21D345EA9@biskalar.de> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: double quoted expansion question MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Sep 7, 5:43pm, Sebastian Stark wrote: } } Wow, thanks. My mistake is that I thought that because the quotes are } at the outermost level, the double quoted joining was not part of this } and applied at the very end. I can see how you might think that, but actually double-quoted-ness applies all the way down the nested expansions from whatever level it first encloses. } For here-docs there seems to be yet another twist: Hmm, that's an odd one -- certainly appears to be a bug. Workaround is to add an otherwise meaningless level of nesting: cat <