From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25686 invoked by alias); 10 Jan 2017 09:39:52 -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: 40320 Received: (qmail 404 invoked from network); 10 Jan 2017 09:39:52 -0000 X-Qmail-Scanner-Diagnostics: from mx.spodhuis.org 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(94.142.241.89):SA:0(-5.5/5.0):. Processed in 14.653096 secs); 10 Jan 2017 09:39:52 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-5.5 required=5.0 tests=RCVD_IN_DNSWL_MED, RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID,UNPARSEABLE_RELAY autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: zsh-workers+phil.pennock@spodhuis.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spodhuis.org designates 94.142.241.89 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201611; h=In-Reply-To:Content-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=9H6opREKMestnE6e1FAN2xdBcbx2rX63/g+UGPlrmkQ=; b=RIN7pZnwhguAjTyN4ovC3T39lO H04Ju94NbV9HG50+L02wSqqEBW7XGG7sO70m8hNJHhZbyaKbfNKSOn7+v13a/IyB6tvggRtFnwmEd 2BVyvez95fp0Nv35y541k+bNdUjn0wkIKqFd+lS6bAy2Mru0qB2hKZhbFV+Oq9Nl/bDZIb+CxJrNG dN0hd61riZIgfrOPL+Q+eJ40M8hj; Date: Tue, 10 Jan 2017 09:39:31 +0000 From: Phil Pennock To: Daniel Shahaf Cc: zsh-workers@zsh.org Subject: Re: [PATCH] Document echo \c behaviour Message-ID: <20170110093931.GA13581@tower.spodhuis.org> References: <20170109203209.GA13324@breadbox.private.spodhuis.org> <20170110035259.GA31866@fujitsu.shahaf.local2> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170110035259.GA31866@fujitsu.shahaf.local2> OpenPGP: url=https://www.security.spodhuis.org/PGP/keys/0x4D1E900E14C1CC04.asc On 2017-01-10 at 03:52 +0000, Daniel Shahaf wrote: > Thanks; I pushed the first hunk. I didn't push the second one because > I don't think it's required. If you disagree then make your case ;-). The behaviour is bug-ass crazy nuts and needs justification. Every other escape sequence is a character which is inserted; \c was always a special case for "suppress the following newline", but "truncate _everything_ else" from an _escape_ sequence is ... face-palm worthy. It warrants explanation as to why it's so counter-intuitive. > P.S. Overly-literal-reading corner: doesn't "All characters following... > will be ignored" mean that «echo 'foo\cbar' 'baz' 'qux'» should be > equivalent to «echo 'foo\cbar' '' ''»? I.e., print «foo» followed by > two trailing spaces? Sounds right. Take it up with the Austin Group. I believe that Bart is masochistic enough to pay attention in those arenas and might be willing to raise it as a spec bug. (I tried following AG for a while, and ran away)