proper terminal capability negotiation

determine support for the kitty protocol and then pick output sequences
accordingly.

tested on ghostty (supports kitty) and tmux-in-ghostty (tmux does not
support kitty protocol) with shift+enter as newline.

1 files changed, 6 insertions, 3 deletions

diff --git a/src/tui_components.zig b/src/tui_components.zig
index 1832fc2..3dfe817 100644
--- a/src/tui_components.zig
+++ b/src/tui_components.zig
@@ -527,6 +527,9 @@ pub const InputBox = struct {
             switch (step.decoded) {
                 .key => |k| self.applyKey(k) catch return,
                 .paste => |p| self.insertText(p) catch return,
+                // Negotiation replies are consumed by the app before input is
+                // routed here; ignore defensively if one slips through.
+                .negotiation => {},
             }
         }
     }
@@ -749,14 +752,14 @@ pub const Footer = struct {
         var fps_buf: [48]u8 = undefined;
         const fps = self.fpsText(&fps_buf);
 
-        // Build the PLAIN content: "<fps>   <model>" (model only if set).
+        // Build the PLAIN content: "<model>   <fps>" (model only if set).
         var plain: std.ArrayList(u8) = .empty;
         defer plain.deinit(a);
-        try plain.appendSlice(a, fps);
         if (self.model.items.len != 0) {
-            try plain.appendSlice(a, "   ");
             try plain.appendSlice(a, self.model.items);
+            try plain.appendSlice(a, "   ");
         }
+        try plain.appendSlice(a, fps);
 
         const vis = truncateToCols(plain.items, width);