Linux file path completion breaks down after it encounters the first path element with a space. about powershell-wsl-interop

[mikebattista]

Spaces in paths is more a Windows thing than a Linux thing, so if the user just uses Windows path resolution for Windows paths (rather than completing through /mnt), this is less problematic.

[mikebattista]

OTOH if your current directory is c:, for example, and you try to resolve "Program Files" or another relative folder with spaces, Linux completion will take over which will recognize the first directory element, but then fail to resolve further.

Believe I'd need to modify how the COMP* variables are setup for paths with spaces in them since they are likely being considered multiple arguments, and the escaped characters might also be interfering with resolution.

[mikebattista]

This seems to be fixed just by surrounding spaced paths with single quotes, though the cursor position needs to be moved to within the closing quote for completion to continue. Will see if that can be resolved later.