bad color ux
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 454
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
On SIGINT, Docker Scout often fails to properly terminate color codes or other terminal escape sequences, causing the terminal to become corrupted.
As a workaround, bash-like shells can run reset. But computers exist to automate, not create busywork.
In general, color codes tend to create more problems than they solve. Recommend disabling all terminal escape codes by default.
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 a SIGINT during Docker Scout CLI output and inspect the terminal behavior afterward. Trace the handling of color and other terminal escape sequences; done means interrupted commands leave the terminal usable and terminal escape codes are disabled by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100