Thank you for reporting this. I see where the problem is occurring, and it only happens for built in match generators for the first word (and only when exec.match is enabled) and for cd etc. It doesn't happen for echo ../../scomplete or for ;echo ../../scomplete or fooexe ../../scomplete or etc -- those normalize all the path separators to backslash.

It turns out that in CMD typing foo/bar means it's actually gets executed as foo /bar. I discovered that as part of updating the input line coloring parser to more accurately match how CMD actually interprets the command line.

And I fixed Clink to work accordingly some time ago. So, this issue 57 is back to "not working".

Except that it's actually technically working properly now. 🙃

Trying to make folder/filename completion work (in the first word on a command line) means that program/flag cannot work. Or vice versa.

I feel that it's appropriate for Clink to match how CMD actually works.

So, I'm going to let issue 57 stay "broken" since that's actually "correct".

Sorry that it's so confusing. Windows and CMD are not the same as Linux and bash, and Clink can't overcome that all by itself, at least not without breaking normal Windows and CMD behaviors (which causes other problems).

Or, if you want to type ../whatever in the first word and use completion, then CMD needs a " inserted: "../whatever will allow completion to work as desired.

I know it isn't like bash or Linux. But this isn't bash or Linux, and it's important to stay compatible with how CMD actually works.