From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12527 invoked by alias); 25 May 2010 14:25:30 -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: 27973 Received: (qmail 27075 invoked from network); 25 May 2010 14:25:19 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) 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.1 Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) MIME-Version: 1.0 In-Reply-To: <10739.1274644720@pws-pc> References: <10739.1274644720@pws-pc> Date: Tue, 25 May 2010 07:00:25 -0700 Message-ID: Subject: Re: ${(q)...} for newline From: Bart Schaefer To: Peter Stephenson Cc: Zsh hackers list Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sun, May 23, 2010 at 12:58 PM, Peter Stephenson wrote: > Param-style simple (i.e. backslash) quoting of a newline appends a real > newline in double quotes. =A0It seems to me it would occasion far fewer > surprises if this never output a literal newline, so this uses $'\n'. I let this stew for a couple of days before commenting ... and after some initial vague unease about this I guess I'm over it, since $'...' is already used for unprintable or invalid characters. However, I suggest that (q-) continue to use the literal quoted newline.