From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] _arguments: Escape colons and backslashes in $opt_args unambiguously.
Date: Thu, 8 Sep 2016 08:49:06 -0700 [thread overview]
Message-ID: <160908084906.ZM13420@torch.brasslantern.com> (raw)
In-Reply-To: <20160908110115.GA1707@fujitsu.shahaf.local2>
On Sep 8, 11:01am, Daniel Shahaf wrote:
}
} Applied both of your suggestions, and added a paragraph:
Thanks. Typo:
} +ambiguity: '-x foo\:bar' (one argument with a backslashed colon) and
} +'-x foo\\ bar' (two argumnets, and the first one ends in a backslash) would
"argumnets"
prev parent reply other threads:[~2016-09-08 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 18:26 Daniel Shahaf
2016-09-07 7:03 ` Bart Schaefer
2016-09-07 22:07 ` Daniel Shahaf
2016-09-08 0:13 ` Bart Schaefer
2016-09-08 11:01 ` Daniel Shahaf
2016-09-08 15:49 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=160908084906.ZM13420@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).