Replace unix path separator on complete

[zdm]

Hi.

Previously, when I type, for example, "./2" and press "TAB" to complete file name - clink replace "./2" with ".\2" and complete filename with the file started with "2" from the current directory.

But after some clink update (I don't remebmer which version exactly) it require me to use windown path separator "\" only.

This is not very suitable.

Could you please tell me, what option in config I should set to restore old behaviour. I belive, that you move it to option )).

Thank you!

[chrisant996]

All changes are listed at Changes in the documentation.

You're looking for this one:

• Added an auto mode for the match.translate_slashes setting. This mode makes completion translate all slashes in the completed word to match whichever kind occurs first in the word, or to the system path separator if there are no slashes yet (e.g. when completing a directory name).

Run clink set match.translate_slashes to see more about the setting.

Run clink set match.translate_slashes system to select the previous behavior of converting forward slashes to backslashes.

[zdm]

Thank you for answer.

I tried auto, system, backslash.

Nothing works. When I am typing "./1" and press TAB - completion just not performed. Slash not changed.

With "backslash" option - when I am typing ".\1" - it works ( change path to "./1" and make completion), bun this is no what I meed.

[chrisant996]

Oh, I understand now. The original description did not mention that completion is not performed, and I thought you were reporting that completion worked but kept the forward slash.

What changed and why

The command line parser was changed to respect how CMD syntax works.

• If you run ./something then CMD interprets that as trying to launch a program . and pass it /something as an argument.
• If you have a subdirectory foo and a script bar.cmd (so there's a file foo\bar.cmd) and you run foo/bar.cmd then CMD interprets that as trying to launch a program foo and pass it /bar.cmd as an argument.

Parsing the command line in Clink now respects that, so that input line coloring can be accurate and so for example you can type dir/Tab and get completions for / flags to dir.

What you want

I understand what you want, and why.

I'll have to think about how that can be accommodated.

[zdm]

Ok, thank you very much. I am wondering, that it worked some time ago.

[chrisant996]

@zdm When completing the first word in a command line:

1. Do you only need completing ./ to convert the slash?
2. Or do you also need somedir/ to convert the slash?

Case 1 is easy to allow an exception for. Case 2 is much more problematic to accommodate, so I'd rather not introduce complexity and inconsistencies for that case.

[zdm]

I am personally use "./xxx" only. It it fast and easy to type when I need to complete filename from the current directory.