zsh completion is too strict on command line args

[laishulu]

Rust Version

rustc 1.17.0-nightly (29dece1c8 2017-02-08)

Affected Version of clap

"clap 2.20.3 (registry+https://github.com/rust-lang/crates.io-index)",
name = "clap"
"checksum clap 2.20.3 (registry+https://github.com/rust-lang/crates.io-index)" = "f89819450aa94325998aa83ce7ea142db11ad24c725d6bc48459845e0d6d9f18"

Expected Behavior Summary

myapp --foo1 bar1 --foo2 bar2 --foo3 bar3 --<tab>
then list candidates for more args.

Actual Behavior Summary

when myapp --foo1=bar1 --foo2=bar2 --foo3=bar3 --<tab> , auto complete works perfect.
but if I use space instead of the = symbol, auto complete doesn't work.

[kbknapp]

I'm not sure I understand the issue entirely. Are you saying the candidates don't include the = but you'd like them to, or there are missing valid candidates?

[laishulu]

when myapp --foo1=bar1 --foo2=bar2 --foo3=bar3 --<tab> , auto complete works perfect.
but if I use space instead of the = symbol, auto complete doesn't work.

[kbknapp]

Ah ok! I understand, thanks.

I think this has to do with how Zsh completion works and isn't specific to clap. In Bash completion scripts there's a way to tell the interpreter that a value follows certain options, but I'm not aware of a way to do this in Zsh.

I'm open to suggestions on how to make the completion generation better.

[segevfiner]

This might have been fixed by #1141. Needs testing.

[pksunkara]

@segevfiner @laishulu I don't have zsh and I tried testing it with mac's default zsh (5.3) and I keep getting _arguments not found. If one of you could test and respond back, that would be great.

[intgr]

By pksunkara's request, I tested with the example program in PR #1793, this issue is fixed.