Document bash.exe from Windows takes precedence over our bash.exe
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3.3k
- Forks
- 446
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 1
Description
See https://github.com/msys2/setup-msys2/issues/52
It's not very common to go from native to cygwin, but it can be confusing if it happens.
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
Start by reading the linked msys2/setup-msys2 issue #52 to understand the Windows bash.exe precedence problem and what users need explained. Locate the relevant MSYS2 homepage documentation, then add guidance describing the native-versus-Cygwin bash.exe confusion and verify that the resulting page clearly documents the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100