mobile-shell / mobile-shell/mosh
interference of clear-to-EOL with pending auto-wrap
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 14.5k
- Forks
- 865
- PR merge metrics
- No merged PRs in 30d
Description
Discovered at https://github.com/mintty/mintty/issues/781.
This is rather obscure-- terminal emulators vary on their handling of the interaction between clear-to-EOL and auto-wrap. Mosh appears to behave as XTerm 333 does, so I don't see a big problem, but the mintty issue argues for a more correct handling.
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 behavior described in mintty/mintty#781 and reproduce the interaction between clear-to-EOL and pending auto-wrap in mosh. The issue names no files, tests, or entry points, so first locate the terminal escape-sequence and auto-wrap handling; done means matching the intended, more correct behavior with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100