From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11786 invoked by alias); 2 Sep 2015 09:03:53 -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: X-Seq: 36398 Received: (qmail 13200 invoked from network); 2 Sep 2015 09:03:52 -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-AuditID: cbfec7f5-f794b6d000001495-4f-55e6bb753f0f Date: Wed, 02 Sep 2015 10:03:47 +0100 From: Peter Stephenson To: zsh workers Subject: Here document in code chunks Message-id: <20150902100347.03027225@pwslap01u.europe.root.pri> In-reply-to: References: Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsVy+t/xK7qlu5+FGtxea2pxsPkhkwOjx6qD H5gCGKO4bFJSczLLUov07RK4Mp49UC6Yx1JxZmp8A2MXcxcjJ4eEgInEjjW9ULaYxIV769lA bCGBpYwS/05UdDFyAdkzmCQu7m5kh3C2Mkoc+LmQBaSKRUBVovnZb0YQm03AUGLqptlgtghI /Ps/sBphIPvF7pfsIDavgL3EggXzWUFsToFgiZefvjFCbAuQ+HbnCxOIzS+gL3H17ycmiIvs JWZeOcMI0Sso8WPyPbCZzAJaEpu3NbFC2PISm9e8ZYaYoy5x4+5u9gmMQrOQtMxC0jILScsC RuZVjKKppckFxUnpuUZ6xYm5xaV56XrJ+bmbGCEB+3UH49JjVocYBTgYlXh4GxKfhQqxJpYV V+YeYpTgYFYS4f2wAyjEm5JYWZValB9fVJqTWnyIUZqDRUmcd+au9yFCAumJJanZqakFqUUw WSYOTqkGxktudhsChAOfR015PWWZmFP/je6n8gHzf3578ivraPbxCGPeNU/Cf99Z772ubU1p yd2G9odbvv6p3fktNOHc02TbuiUxS3TbD27zXlFX+0olX8Mj67NrxJ7Kq9clwnjaZbXiovNm Xfs2oSXmwvLkH16bmU9Zz5i7+qXzvjmabIqS20+m+p2cfVCJpTgj0VCLuag4EQD06i5DVAIA AA== On Wed, 2 Sep 2015 10:50:07 +0200 Mikael Magnusson wrote: > Just got this report on #zsh, > > % f() { cat << x << y; } > foo > x > bar > y > % which f > f () { > cat < foo > xbar > y > } > > There should be a newline between x and bar in the output. The > function itself works fine. Looks like this isn't especially new --- was present in 5.0.0 --- so while this ought to be easy enough to fix and go into the next release, it's not especially related to 5.1 / 5.1.1, either. pws