mintty doesn't set terminal io properly
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3.3k
- Forks
- 446
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 1
Description
This appears to be a bug in the msys mintty compile. I can run the same version of mintty (3.5.2) from cygwin and it works correctly.
Reproduce by starting MSYS2 MSYS from the start menu on Windows 10. The terminal window opens and bash starts correctly.
Run the windows version of python
python -c "import os,sys; print(os.isatty(sys.stderr.fileno()))"
and it returns False. Doing the same thing with cygwin returns True.
Possibly related?
When MSYS bash starts most of the windows path has been removed instead of converted. All that gets converted is
/c/Windows/System32
/c/Windows
/c/Windows/System32/Wbem
/c/Windows/System32/WindowsPowerShell/v1.0
I don't know if this is by design or a problem.
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 issue by starting MSYS2 MSYS on Windows 10 and running the provided Python command, then compare its stderr TTY result with Cygwin. Investigate the MSYS mintty 3.5.2 behavior and the reported PATH conversion, using the related details in the issue as starting points. Done means Windows Python reports stderr as a TTY in MSYS and the intended PATH behavior is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, python
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100