Possible solution for name conflicts
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- bash, rust
- Domain
- cli, operating-systems
Research direction
Start with the conflict example in README.md at the linked section and compare it with the proposed cmd/conhost handling of C:\Windows\System32\expand.exe. Clarify how encoded paths, PATH-based POSIX commands, and a bash.exe entry point should work together, then define tests or observable command behavior that demonstrate legacy .bat/.cmd files remain unaffected.
Written by the indexing model from the issue text.
Description
As an example, the readme mentions conflicts:
https://github.com/microsoft/coreutils/blob/bc282d5c349fab94bb769da75a6e91bd9032f784/README.md?plain=1#L61
The expand command appears to be a utility located in:
C:\Windows\System32\expand.exe
Solution: Ignore variables and encode the file address inside the source code of cmd/conhost.
Example: %SystemRoot%\System32\expand.exe
Any legacy *.bat or *.cmd file is executed by cmd/conhost, without breaking anything.
Newer shells can use posix expand by calling it through the PATH variable set to a different directory.
In this case, it would also be useful to create a bash.exe file that executes sh scripts, uses bash syntax, and only calls these coreutils.
- Dominant language
- Rust
- Stars
- 5.2k
- Forks
- 107
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 4
Contributor guide
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.
More from microsoft/coreutils
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
sleep has 9MB Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
grep not work Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
All issues in microsoft/coreutils
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100