From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20924 invoked by alias); 27 Sep 2011 14:20:44 -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: 16447 Received: (qmail 16 invoked from network); 27 Sep 2011 14:20:34 -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 closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <110927072015.ZM25125@torch.brasslantern.com> Date: Tue, 27 Sep 2011 07:20:15 -0700 In-reply-to: Comments: In reply to Ismail Donmez "Re: Interesting zsh behaviour regarding awk and backslash" (Sep 27, 3:54pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh Users Subject: Re: Interesting zsh behaviour regarding awk and backslash MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Sep 27, 3:54pm, Ismail Donmez wrote: } } Thanks that works, any reason this is not on by default for sh } compatibility though? Because zsh is quite deliberately not sh compatible by default?