Tip: busybox-w32 shell option -d allows you to specify the current directory of the new shell
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 4.8k
- Forks
- 381
- PR merge metrics
- No merged PRs in 30d
Description
A helpful feature I just found:
busybox-w32 has an undocumented shell option -d which allows you to specify the current directory of the new shell. This has to appear before the -s or -c options.
Source: https://github.com/rmyorston/busybox-w32/issues/211#issuecomment-792578645
With ..\w64devkit\bin in your PATH you could do the following in Windows PowerShell or cmd :
> sh -d \path\to\working\folder
and get in your busybox-w32 session:
/path/to/working/folder $
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
The issue records the undocumented busybox-w32 sh -d option and links to its source discussion, but names no documentation file or test. Start by locating the project's documentation for launching shells on Windows; done means the behavior and command example are documented in the appropriate location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, shell
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100