# Change codepage 932 to 65001 temporary
~> chcp 65001
Active code page: 65001
~> ps | where name == pwsh.exe | select pid name
╭───┬───────┬──────────╮
│ # │ pid │ name │
├───┼───────┼──────────┤
│ 0 │ 19368 │ pwsh.exe │
╰───┴───────┴──────────╯
# kill command succeeds.
~> kill 19368
SUCCESS: Sent termination signal to the process with PID 19368.
If we don't use encoding sniffers such as chardetng, we seem to need to map all possible Windows internal encoding type representations one by one. Looks like a very troublesome repetitive task :(.
Describe the bug
I tested on Nushell 0.96.0 in Japanese Windows 11.
kill
command fails with the following message in a non-English Windows environment.The steps to reproduce are as follows,
There are two workarounds.
Workaround 1 : Use taskkill command directly
Workaround 2 : Change codepage temporary
How to reproduce
kill
command.Expected behavior
The process is killed without errors.
Screenshots
No response
Configuration
Additional context
No response