alpha
Login
or
Join now
ptr.pet
/
ghostty
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
ghostty
/
src
/
inspector
/
widgets
/
at
main
9 files
Alex Bennett
terminal: support click_events=2
2mo ago
3263ce51
key.zig
terminal: support click_events=2
2 months ago
page.zig
inspector: hyperlinks
6 months ago
pagelist.zig
inspector: cell inspector
6 months ago
renderer.zig
renderer: semantic prompt overlay
6 months ago
screen.zig
terminal: support click_events=2
2 months ago
style.zig
inspector: move style to widgets dir
6 months ago
surface.zig
terminal: fix selection gesture edge cases Selection gestures now treat releases with invalidated anchors as dragged, so a press that crosses screen boundaries cannot also activate links or prompt clicks on release. Cell drags that create a same-cell selection also mark the gesture as dragged, which keeps click-only actions from firing after a threshold-crossing drag. Autoscroll now resolves the drag pin after moving the viewport instead of reusing the pin from before the scroll. This keeps the selection aligned with the row currently under the pointer. The inspector also validates the tracked click pin before displaying it so stale pins from inactive screens are ignored.
2 months ago
terminal.zig
inspector: starting screen
6 months ago
termio.zig
terminal: make stream processing infallible The terminal.Stream next/nextSlice functions can now no longer fail. All prior failure modes were fully isolated in the handler `vt` callbacks. As such, vt callbacks are now required to not return an error and handle their own errors somehow. Allowing streams to be fallible before was an incorrect design. It caused problematic scenarios like in `nextSlice` early terminating processing due to handler errors. This should not be possible. There is no safe way to bubble up vt errors through the stream because if nextSlice is called and multiple errors are returned, we can't coalesce them. We could modify that to return a partial result but its just more work for stream that is unnecessary. The handler can do all of this. This work was discovered due to cleanups to prepare for more C APIs. Less errors make C APIs easier to implement! And, it helps clean up our Zig, too.
5 months ago