Read terminal color codes in daemon client on every run
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Currently terminal color codes are read once during daemon start-up, and then re-used on each run. So if the daemon is started in one environment (e.g. an IDE plugin) where colors are not available, and then run in another where they are available (e.g. a normal terminal), the colors stay disabled until the next daemon restart.
This is probably low priority because people don't often switch between running mypy daemon in a terminal and in IDE, and this doesn't cause mangled formatting.
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.
Research direction
Start by tracing where the mypy daemon client reads terminal color availability during daemon startup and where each run reuses that value. Done means color availability is checked for every run, including when switching between an IDE environment and a normal terminal, without requiring a daemon restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100