sh is borked on 2.0.0
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 4.8k
- Forks
- 381
- PR merge metrics
- No merged PRs in 30d
Description
Upstream: https://github.com/rmyorston/busybox-w32/issues/447
~/scoop/apps/w64devkit/current $ which ls
sh: unable to spawn shell
~/scoop/apps/w64devkit/current $ bash
sh: unable to spawn shell
~/scoop/apps/w64devkit/current $ cd ..\..
sh: cd: can't cd to ....: Invalid argument
~/scoop/apps/w64devkit/current $ cd ..\
> /
sh: cd: can't cd to ../: Invalid argument
~/scoop/apps/w64devkit/current $ cd ..
sh: cd: can't cd to ..: Invalid argument
~/scoop/apps/w64devkit/current $ cd ../..
sh: cd: can't cd to ../..: Invalid argument
~/scoop/apps/w64devkit/current $ env
sh: unable to spawn shell
~/scoop/apps/w64devkit/current $ cd
sh: cd: can't cd to C:/Users/????: Invalid argument
~/scoop/apps/w64devkit/current $
~/scoop/apps/w64devkit/current $ cd
sh: cd: can't cd to C:/Users/????: Invalid argument
If it helps, I'm running Windows 11 21H2.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the shell, spawn, and cd failures on Windows 11 21H2, then compare the behavior with upstream issue 447. The work is done when sh can spawn commands and navigate to parent directories without the reported invalid-argument errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100