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
/
terminal
/
osc
/
parsers
/
at
main
15 files
Alex Bennett
fix: fix tests, change enum fields to lowercase
2mo ago
97777cf5
change_window_icon.zig
fix: fix tests, change enum fields to lowercase
2 months ago
change_window_title.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
clipboard_operation.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
color.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
context_signal.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
hyperlink.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
iterm2.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
kitty_clipboard_protocol.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
kitty_color.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
kitty_text_sizing.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
mouse_shape.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
osc9.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
report_pwd.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
rxvt_extension.zig
terminal: redo trailing state capture in OSC parser Trailing state capture now is encapsulated in a struct `Capture` and all parsers access the data via `p.capture.trailing()` rather than directly from the writer. This is primarily to prep for the OSC parser to be able to capture the entire sequence (not just the trailing part) so we can setup libghostty for fallback handlers so libghostty implementers can have custom OSC behaviors. But, it has the benefit of making our OSC parser much cleaner too.
4 months ago
semantic_prompt.zig
fix: fix tests, change enum fields to lowercase
2 months ago