Case (in)sensitive files in macOS
Open
Nobody has claimed this yet.
Core
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
M2 shouldn't confused a file in the same directory named `elimination.m2` with the package `Elimination.m2`, even if it's running on macOS. This causes too many head scratching confusions for people.
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 reproducing the package-versus-file name collision on macOS using a directory containing `elimination.m2` and the package `Elimination.m2`. Trace the file and package lookup entry points, then add or run focused coverage showing that the two names are not confused on macOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100