From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20936 invoked by alias); 8 Sep 2016 01:06:35 -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: 39233 Received: (qmail 23591 invoked from network); 8 Sep 2016 01:06:35 -0000 X-Qmail-Scanner-Diagnostics: from mail-pa0-f54.google.com 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(209.85.220.54):SA:0(0.0/5.0):. Processed in 0.599435 secs); 08 Sep 2016 01:06:35 -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=0.0 required=5.0 tests=T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=21z2L6PZaVbPUWPX+58PduQpqvHOWvzyqU1RavZK2Is=; b=lebrw7pFuTC8iGp/LVFygorNFEUwb8DzxJw6vKbFgMNduOXzz9TIwxcGA1R1+6TBQC oIQ+SC6DZIBL+Uqg50TiSZEQ+OxqLBmIP5jltDuf5LQQWihkbzbP9nVgtOwOZ/gQ0vAv OjlIr4ILvZj+gskg5MFDrR0eo3k6bldEDcYfdVwE/2bxlTgRLMTjEHD0eeUB7746BZv8 6icbdhThH3t3KAMjCF3fhqAxKnMhy+oZKfobLM545EGZ77U9SouKeWt2lw4vytUDjRYH JH/FZSYt9mAh6Eodnr/QZ+6E1rKjaI43LPJpGiyPGmiVprPomwobs1fC9CatEFvCRMlI vYfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=21z2L6PZaVbPUWPX+58PduQpqvHOWvzyqU1RavZK2Is=; b=Z0x4AnwpoU/DlnbwXc/1xMkL7Jyv/KsT0/15tcYm6uthKrs2MiEkAHB5yON2TFIDtX Rc/W43AxO9g3Ef8OJO3lOujEA8urBuh05EH1Fs1HKdvy8owoE0tgJG67UMLkfUsuhHMn Jer9xd+xgT8/87hlfXM/zAQxk5cByIANG7XBRoQKy4XnYp1lHxtcRxA6bwhBPA5TkPL0 ZsenXCoL7x+0QwQrTocfqZm/T6JEmJI5D037c8YobkwFYjmU4D5s7LOmBr7Z7DO8rV+k +odSrB90xTlOYEKRp//zHPzCNIhSHPTjQFw2k0Wli/fvr7IBci0RPCEHaEbY3FbLEEpm pZoA== X-Gm-Message-State: AE9vXwOL3TK0EBClAOPaiRdF7vfOpsiViRhdc2LGhIa0skwlbafGpFsTgSeqPp7g8KX4+g== X-Received: by 10.67.23.70 with SMTP id hy6mr66689429pad.75.1473293637197; Wed, 07 Sep 2016 17:13:57 -0700 (PDT) From: Bart Schaefer Message-Id: <160907171356.ZM14819@torch.brasslantern.com> Date: Wed, 7 Sep 2016 17:13:56 -0700 In-Reply-To: <20160907220701.GA7775@fujitsu.shahaf.local2> Comments: In reply to Daniel Shahaf "Re: [PATCH] _arguments: Escape colons and backslashes in $opt_args unambiguously." (Sep 7, 10:07pm) References: <1473013592-24926-1-git-send-email-danielsh@fujitsu.shahaf.local2> <160907000320.ZM11510@torch.brasslantern.com> <20160907220701.GA7775@fujitsu.shahaf.local2> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: [PATCH] _arguments: Escape colons and backslashes in $opt_args unambiguously. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 7, 10:07pm, Daniel Shahaf wrote: } Subject: Re: [PATCH] _arguments: Escape colons and backslashes in $opt_arg } } Bart Schaefer wrote on Wed, Sep 07, 2016 at 00:03:20 -0700: } > On Sep 4, 6:26pm, Daniel Shahaf wrote: } > } } > } Is it okay to refer to NEWS from the manual? } > } > Are there any other examples of the manual referring directly to the } > behavior of previous versions? } } Yes: CONTINUE_ON_ERROR in zshoptions(1). (And the usage examples under } is-at-least, but that doesn't count.) } } > It's not the kind of thing it's easy to search for, } } I found that with: } . } ag -C 3 -G 'yo$' '[345][.][0-9]' Doc/Zsh } . I suspect "ag" is the same thing I have installed as "ack". ack -C 1 -G .yo$ version Doc | grep -i /Zsh/.\*zsh which should have found all mentions of "version" and "zsh" on the same or adjacent lines. Found the 5.0.1 reference, and a remark about "the restriction in older versions of zsh" in params.yo discussion of export. } I'm happy to drop the note entirely, or to drop the reference to NEWS } and keep the sentence stating the behaviour difference. CONINUE_ON_ERROR was a *lot* more significant change than this -- I'd classify backslashing the backslashes as a bug fix, and we don't usually call those out in the manual. Anyway this has probably now had more thought than it was worth. } > } +ambiguity: if the -x option took two arguments (as in } > } + _arguments : -x:foo:${action}:bar:$action } > } +), it would be impossible to tell from $opt_args whether the command-line } > } +was '-x foo\:bar' or '-x foo\\ bar'. } > } > Is this example correct? Isn't the actual ambiguity between } > [[[ -x foo\:bar ]]] (one arg) and [[[ -x foo bar ]]] (two args)? } } > If I'm wrong, what is it about your explanation that confused me? } } I don't know. Sometime after I'd sent that message, it occurred to me that the phrase "two words where the first ends in a backslash cannot be distinguished from one word with a backslashed colon in the middle" was what you were getting at all along, and that indeed the example was correct. Maybe just write that out?