You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experimenting with handling completions completely in clap_complete, like python's argcomplete. As an input, I'm getting COMP_LINE which is an environment variable containing the line being parsed, ie an OsStr. I'm wanting to be able to handle non-unicode paths which means I can't operate on OsStr::to_str but need to convert to the raw bytes via os_str_bytes. It looks like shlex operates on bytes internally but doesn't offer a constructor or outputs that stay within bytes.
If you are open to this, I'd be willing to implement support for it.
The text was updated successfully, but these errors were encountered:
FYI I found I could implement completions in a different way which also saves a lot on complexity, so this is no longer a blocker for me. Its unclear if this new strategy will work universally and I won't ever need this or if I might end up needing this eventually.
I'm experimenting with handling completions completely in
clap_complete
, like python's argcomplete. As an input, I'm gettingCOMP_LINE
which is an environment variable containing the line being parsed, ie anOsStr
. I'm wanting to be able to handle non-unicode paths which means I can't operate onOsStr::to_str
but need to convert to the raw bytes viaos_str_bytes
. It looks likeshlex
operates on bytes internally but doesn't offer a constructor or outputs that stay within bytes.If you are open to this, I'd be willing to implement support for it.
The text was updated successfully, but these errors were encountered: