non‐ASCII characters in path (and thus prompt) confuse clink in Powershell

[deepestblue]

I use clink in Powershell and it seems to work well. I navigated to a directory with non‐ASCII characters in its name ('saṁskr̥tam'), and tab-completion stopped working. The FAQ mentions some tricks clink does to read the Powershell prompt, so maybe that code is acting up?

clink in cmd.exe works fine.

[mridgers]

As Powershell doesn't change the process' active directory like cmd.exe does when navigating around using "cd", Clink runs a regular expression on the prompt to extract the path (in powershell.lua). Looks like Lua's ".*" doesn't work with UTF8 strings.

[mridgers]

Jumped the gun there. Lua's fine - it is Clink that needs to convert UTF8 strings from Lua where appropriate.

[VeryTastyTomato]

It seems that this issue still occurs. I use Cmder which uses Clink, and it displays paths with non-ASCII characters incorrectly. I opened a ticket on their GitHub repository if you want more information, but to summalize I get the following error message: attempt to call a nil value.