mobile-shell / mobile-shell/mosh
Undocumented behavior: mosh drops exit code of command executed on target, returns overall session success instead
Open
Nobody has claimed this yet.
docs
feature
good first issue
- Dominant language
- C++
- Stars
- 14.5k
- Forks
- 865
- PR merge metrics
- No merged PRs in 30d
Description
I would expect mosh --local 127.0.0.1 "sh -c 'exit 42'" ; echo $? to exit with code 42 as does ssh, but it exits with 0. Is this behavior intentional?
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 the command in the issue and comparing its exit status with ssh. Trace how mosh determines the overall session status, then verify that the documented or intended behavior is clear and that the command's exit status is handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100