From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-39207-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 7818 invoked by alias); 7 Sep 2016 07:03:30 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 39207
Received: (qmail 23973 invoked from network); 7 Sep 2016 07:03:30 -0000
X-Qmail-Scanner-Diagnostics: from mail-pf0-f170.google.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.192.170):SA:0(0.0/5.0):. 
 Processed in 0.151376 secs); 07 Sep 2016 07:03:30 -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=AW1FSOfmr/ILKTNP7WE5A/HGxYOzRrf2+6rFoNW46dg=;
        b=dMnr1f/CMae+5Oq1aYjXyG5vAzeFotnu+/DDEksjfqS7MpM1CUJHzjB5yoHBLa8rnb
         kZh+7sIkGWsMm4mpmAXVHy6iRjI88utKuzrhTSTAfPR4nd/C1fa6FNOuCacqSZJ6Ue8A
         9oyiiv3NFnUdQEyWaxnRSMdsWS9/N/5H86FzSasVya1UJ1qluLtwlMF3lW8bQmCJKQ6+
         d4rp8aGYn0Mjv19kYMOfMYU16Rbau84VuGM9DJMNIYBhXugN8YRv6y46wT/MIUX0fOHO
         mmq8NYxiFXSv6uXrmkwrwpcOMXGwqksjkJi77QbUK6J0bziYiSD9f2+w7oXJiD8GsIHg
         RJ4A==
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=AW1FSOfmr/ILKTNP7WE5A/HGxYOzRrf2+6rFoNW46dg=;
        b=EBTkpMH6nJTieB7sgzU6bh6m0j9V40rg8iXjOJTqg1PIavdcBn3Eo17jVyo50jZK55
         fx7ftXmSRwg1vVicfiIzDiVVXuCWg7z+4IQp428yz1u9bkQIwHxf1tKmihh0g9P9HkFG
         AJE/twwO0BO4pcl93UlT4tT2gEgkAE0TgNl6dB2HNJGKToMbsq6LjY+eeR1LzKvEublp
         nLBltRyKmLLtpCXagysrWykLHEZXeMWMC1HFZ+5O8xrmWSNXwEJXkjA6bIOXK4nwkwJr
         FLQQIre+7lPvKqm7G/6IZoQP3G0UqjVi33SEnayNlc4L51cpbaqY1LSAqVdnJeJRW0z8
         7Vmg==
X-Gm-Message-State: AE9vXwNDJWRTiz6gt4xafPOIHGHjX0Ts1mkPppLwkNMyDYIUwv57Io6lrxQr3dzPT2o3VA==
X-Received: by 10.98.106.65 with SMTP id f62mr79293965pfc.107.1473231803374;
        Wed, 07 Sep 2016 00:03:23 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160907000320.ZM11510@torch.brasslantern.com>
Date: Wed, 7 Sep 2016 00:03:20 -0700
In-Reply-To: <1473013592-24926-1-git-send-email-danielsh@fujitsu.shahaf.local2>
Comments: In reply to Daniel Shahaf <d.s@daniel.shahaf.name>
        "[PATCH] _arguments: Escape colons and backslashes in $opt_args unambiguously." (Sep  4,  6:26pm)
References: <1473013592-24926-1-git-send-email-danielsh@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 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?

It's not the kind of thing it's easy to search for, but I can't think
of any, so my inclination would be to drop your parenthetical Note:.

} In the manual I wrote "See NEWS" even though the pointed-to text is in
} README because (a) NEWS includes README by reference, (b) I doubted
} readers would follow a reference to README in that context.

I doubt readers will follow a NEWS reference either.  If this is
important enough to reference -- which I don't think it is -- then
it's important enough to say it here, not cross-reference somewhere
outside of the regular documentation tree, and certainly it shouldn't
require going to NEWS, finding nothing, and then having to realize
it might be in README.

} +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?

There's probably still an ambiguity between [[[ -x foo bar ]]] and
[[[ -x foo -x bar ]]] ...