aboutsummaryrefslogtreecommitdiff
path: root/vendor/libghostty-vt/src/terminal/kitty/dnd.zig
diff options
context:
space:
mode:
authorCan Celik <ogulcancelik@gmail.com>2026-09-10 21:51:57 +0300
committerGitHub <noreply@github.com>2026-09-10 21:51:57 +0300
commit425c86179791cd32e2d4ce0ae7f269940b4b0663 (patch)
treee52c4383a6d69216cbe2a32638bf90841d7e2189 /vendor/libghostty-vt/src/terminal/kitty/dnd.zig
parent90e947a6e26e02f10ec7f1694c4eb5b78a86406b (diff)
chore: upgrade libghostty and preserve terminal behavior (#3906)
Diffstat (limited to 'vendor/libghostty-vt/src/terminal/kitty/dnd.zig')
-rw-r--r--vendor/libghostty-vt/src/terminal/kitty/dnd.zig69
1 files changed, 69 insertions, 0 deletions
diff --git a/vendor/libghostty-vt/src/terminal/kitty/dnd.zig b/vendor/libghostty-vt/src/terminal/kitty/dnd.zig
new file mode 100644
index 00000000..3142a415
--- /dev/null
+++ b/vendor/libghostty-vt/src/terminal/kitty/dnd.zig
@@ -0,0 +1,69 @@
+//! Kitty drag and drop protocol (OSC 72).
+//!
+//! Specification: https://sw.kovidgoyal.net/kitty/dnd-protocol/
+//!
+//! The protocol lets a program running in the terminal participate in
+//! native OS drag and drop. A client registers to accept drops (t=a);
+//! the terminal then forwards native drag movement (t=m) and drops
+//! (t=M) to it and serves the dropped data on request (t=r), instead
+//! of the traditional behavior of pasting dropped paths or text.
+//!
+//! ## Divergences
+//!
+//! These will be fixed in the future:
+//!
+//! * Dropped data is captured eagerly at drop time from a curated
+//! set of representations the embedder can serve (typically
+//! text/uri-list and text/plain), rather than fetched from the OS
+//! on demand. Consequently the native drag session concludes at
+//! drop time and the client's concluding operation (t=r with
+//! x=y=Y=0) only frees the held data, and kitty's 128-entry
+//! request queue and EMFILE overflow handling are unnecessary
+//! because requests are served synchronously in order.
+//! * Every client is treated as local: machine IDs (t=a:x=1) are
+//! accepted and ignored, responses never carry the X=1 remote
+//! marker, and remote file transfer requests (t=r with y or Y
+//! keys) are answered with EINVAL. A remote client (e.g. over
+//! ssh) can still receive text drops; only file-content transfer
+//! is unavailable.
+//! * The terminal never initiates drags (drag out): enabling and
+//! disabling offers (t=o:x=1, t=o:x=2) are accepted and ignored,
+//! and since the terminal never sends a drag start request a
+//! conforming client never offers a drag. Direct offers (t=o:x=0)
+//! and drag data/start commands (t=p, t=P) are refused with EPERM.
+//!
+//! These are on purpose forever:
+//!
+//! * Responses echo the requesting command's terminator (ST or BEL)
+//! per ghostty convention; kitty always uses ST. Terminal-
+//! initiated events always use ST.
+
+const dnd_command = @import("dnd_command.zig");
+const dnd_response = @import("dnd_response.zig");
+const dnd_drop = @import("dnd_drop.zig");
+
+pub const EventType = dnd_command.EventType;
+pub const Metadata = dnd_command.Metadata;
+pub const Operation = dnd_command.Operation;
+pub const Operations = dnd_command.Operations;
+pub const Request = dnd_command.Request;
+pub const Chunking = dnd_command.Chunking;
+
+pub const Errno = dnd_response.Errno;
+pub const RequestKeys = dnd_response.RequestKeys;
+pub const encode = dnd_response.encode;
+pub const encodeError = dnd_response.encodeError;
+
+pub const State = dnd_drop.State;
+pub const Item = dnd_drop.State.Item;
+pub const MoveEvent = dnd_drop.State.MoveEvent;
+pub const max_mime_list_bytes = dnd_drop.max_mime_list_bytes;
+pub const handleCommand = dnd_drop.handleCommand;
+pub const Event = dnd_drop.Event;
+
+test {
+ _ = dnd_command;
+ _ = dnd_response;
+ _ = dnd_drop;
+ _ = @import("dnd_test.zig");
+}