mobile-shell / mobile-shell/mosh
urxvt and Putty Home/End don't work in Mosh
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 14.5k
- Forks
- 865
- PR merge metrics
- No merged PRs in 30d
Description
urxvt (aka rxvt-unicode) sends CSI7~ and CSI8~ for Home, End respectively.
With TERM=rxvt-unicode, bash will interpret these correctly and jump to the beginning/end of the line.
Screen sets TERM=screen and translates them to CSI1~ and CSI4~, which bash also understands.
But Mosh sets TERM=xterm and does no translation, so bash gets confused.
If I tell urxvt (by X resource) to send CSI1~ then my local bash is confused. If I tell it to use CSIH and CSIF, the Xterm codes, then most things work, but Barnowl doesn't recognize these codes (which could be a Barnowl bug).
I don't know if this is related to #161.
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 reviewing the terminal-key behavior described in issue #178 and the related #161 discussion; the payload names no source file or test entry point. Compare the expected Home/End behavior across urxvt, PuTTY, screen, xterm, bash, and Barnowl, and resolve the translation behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100