shell-pool / shell-pool/shpool
Add support for kitty's terminal protocol
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 67
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 15
Description
It seems shpool happily passes on escape sequences to the outer shell, which makes it work great with kitty's graphics protocol. But I guess it doesn't save those escape sequences, and so if I disconnect and reconnect, the images are lost. It probably doesn't make sense to store all escape sequences, but storing specifically those for the graphics protocol would be amazing.
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
Read the kitty graphics protocol documentation linked in the issue, then inspect how shpool currently passes terminal escape sequences through and handles reconnects. Define which graphics-protocol sequences must be retained and verify that kitty images survive a disconnect and reconnect without storing unrelated escape sequences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100