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
Clink 0.4.9 completes net -x:"Tab the same as net Tab. The argmatcher gets confused. The confusion can further be seen where net -x:"config" Tab completes the same as net config Tab and possible completions are server, workstation.
Clink 1.x should:
Not treat -x: (with no following space)` completions as part of the current argmatcher system.
By default allow file completions to occur there.
Have some argmatcher syntax to supply a match generator function attached to a flag (with no following space). Maybe "-x:"+function_name, by overloading the + operator?
(FWIW, probably point 3 will end up superseding point 1, such that technically the argmatcher system does handle -x: completions, but just analyzes the input a little differently.)
The text was updated successfully, but these errors were encountered:
Clink 0.4.9 accidentally interpreted the next part as the next arg
position. But that's because Clink and Readline got out of sync about
which word was being completed.
Clink 1.x didn't do any completion. Although that was actually the
intended behavior, I want to strike a balance between compatibility and
reasonable behavior.
So now Clink recognizes the `-x:` flag syntax and does file completion,
and also colors the whole argument as a flag, regardless what follows
the `:` or `=` character. To generate other matches, a lua script can
register a generator and provide code to handle the case.
This fixes issues #61 and #62.
Clink 0.4.9 completes
net -x:"
Tab the same asnet
Tab. The argmatcher gets confused. The confusion can further be seen wherenet -x:"config"
Tab completes the same asnet config
Tab and possible completions areserver
,workstation
.Clink 1.x should:
-x:
(with no following space)` completions as part of the current argmatcher system."-x:"+function_name
, by overloading the+
operator?(FWIW, probably point 3 will end up superseding point 1, such that technically the argmatcher system does handle
-x:
completions, but just analyzes the input a little differently.)The text was updated successfully, but these errors were encountered: