-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Shim path with umlauts is not encoded in utf-8 #4784
Comments
/cc @niheaven EDIT: a similar issue exists in installing app(creating shortcut) also.
|
Yes, apparently, that is what is in the shim. It is in all shims so the questions is whether there needs to be some encoding changed or turned on. |
Did you face this issue just today or before today also? |
Other days as well. I noticed for the first time a few weeks ago when using adb which needed to be launched directly from the dir to bypass the wrong shim path. As of today, it started happening with other commands too. |
We have |
|
i simply created a user with samename as @kunago in the VM. |
As it seems, I am uble to run "scoop" from cmd with powershell at the beginning. While simply running The problem can be partially solved this way which is the way I am using now to run scoop. However, the umlauts in *.shim files returns an error anytime running any other app from the command line. For instance running Do you know of a workaround for this use case? |
Wait for scoop version bump, and reset all your shims may help. And if bugs are still there, please report again. |
Bug Report
Current Behavior
Often when I try to run commands I receive an error because of the path. My username contains a space and umlauts. Unfortunately scoop does not seem to use utf-8 or so it seems. So instead of "á" in the username in the path I see a question mark instead which obviously results in an error. This is a current issue, I guess a month old.
Expected Behavior
I expect the path to be encoded correctly with umlauts as well.
Additional context/output
Possible Solution
System details
Windows version: [e.g. 7, 8, 10]
Windows 11
OS architecture: [e.g. 32bit, 64bit]
64bit
PowerShell version: [output of
"$($PSVersionTable.PSVersion)"
]Additional software: [(optional) e.g. ConEmu, Git]
I also use conemu but in this case it happens also with pure PowerShell
Scoop Configuration
The text was updated successfully, but these errors were encountered: