Hi Kit,
Are you planning to contribute any of the changes in ghostty-rootshell back to upstream Ghostty or to libghostty-spm, particularly the changes related to iOS input and mouse support?
I'm working on the mobile app for Orca, and I plan to use Ghostty as the terminal engine. Mouse support is especially important for making terminal applications reasonably usable on iPhone and iPad, and rootshell already seems to have done a lot of the work I would otherwise need to build myself.
I'd like to reuse your additions around this functionality rather than independently reimplementing them.
I'm mostly trying to decide how I should structure the dependency:
- If these changes, or at least the generally useful
libghostty parts of them, are intended to be contributed upstream, I can build around upstream Ghostty and expect to converge on those APIs as they land.
- If you expect them to remain rootshell-specific downstream changes, I'll probably use
ghostty-rootshell directly and track your fork instead.
I'm not necessarily asking whether the entire iOS integration can be upstreamed. I'm particularly interested in whether the reusable input, touch/mouse, and related libghostty changes are things you intend to propose upstream.
Thanks for publishing the fork. It is extremely useful reference material for anyone trying to build a serious Ghostty-based terminal on iOS.
Hi Kit,
Are you planning to contribute any of the changes in
ghostty-rootshellback to upstream Ghostty or tolibghostty-spm, particularly the changes related to iOS input and mouse support?I'm working on the mobile app for Orca, and I plan to use Ghostty as the terminal engine. Mouse support is especially important for making terminal applications reasonably usable on iPhone and iPad, and rootshell already seems to have done a lot of the work I would otherwise need to build myself.
I'd like to reuse your additions around this functionality rather than independently reimplementing them.
I'm mostly trying to decide how I should structure the dependency:
libghosttyparts of them, are intended to be contributed upstream, I can build around upstream Ghostty and expect to converge on those APIs as they land.ghostty-rootshelldirectly and track your fork instead.I'm not necessarily asking whether the entire iOS integration can be upstreamed. I'm particularly interested in whether the reusable input, touch/mouse, and related
libghosttychanges are things you intend to propose upstream.Thanks for publishing the fork. It is extremely useful reference material for anyone trying to build a serious Ghostty-based terminal on iOS.