aboutsummaryrefslogtreecommitdiff
path: root/working/eat-sixel-patch/takuzu-original-bug-report.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-19 21:50:08 -0500
committerCraig Jennings <c@cjennings.net>2026-07-19 21:50:08 -0500
commit7483eb390188005e54d1e5f1e9d2789b64ad8fe4 (patch)
tree41c75ed9a3db210acc41e05a20df13e57c9af798 /working/eat-sixel-patch/takuzu-original-bug-report.org
parent18bcd567d1e7770b4e28c43eeefbf81696e2f4a3 (diff)
downloaddotemacs-7483eb390188005e54d1e5f1e9d2789b64ad8fe4.tar.gz
dotemacs-7483eb390188005e54d1e5f1e9d2789b64ad8fe4.zip
chore: version active working artifacts
I made working/ a versioned home for in-progress project artifacts and moved disposable scratch to temp/. This preserves the full music UI design history and the deferred EAT XTWINOPS upstream patch.
Diffstat (limited to 'working/eat-sixel-patch/takuzu-original-bug-report.org')
-rw-r--r--working/eat-sixel-patch/takuzu-original-bug-report.org17
1 files changed, 17 insertions, 0 deletions
diff --git a/working/eat-sixel-patch/takuzu-original-bug-report.org b/working/eat-sixel-patch/takuzu-original-bug-report.org
new file mode 100644
index 00000000..02107a88
--- /dev/null
+++ b/working/eat-sixel-patch/takuzu-original-bug-report.org
@@ -0,0 +1,17 @@
+#+TITLE: Bug/investigate: images from Claude Code don't display in th
+#+SOURCE: from takuzu
+#+DATE: 2026-07-11 14:41:39 -0500
+
+Bug/investigate: images from Claude Code don't display in the EAT terminal.
+
+Context: running Claude Code inside EAT (eat 0.9.4 from elpa). When the agent posts an image to the terminal, nothing renders — Craig can't see it.
+
+Finding: EAT *does* have Sixel image support. eat.el defines eat-sixel-scale, eat-sixel-aspect-ratio, eat-sixel-render-formats, and a full Sixel decode/render path (sixel-buffer, sixel-palette, sixel-render-format, etc.). So the capability exists; this isn't a plain 'EAT can't do images' limitation.
+
+Likely causes to check:
+1. Protocol mismatch: Claude Code CLI probably emits the kitty graphics protocol or the iTerm2 inline-image protocol (OSC 1337), NOT Sixel. EAT renders Sixel only, so a kitty/iTerm image sequence is dropped. Confirm which protocol Claude Code uses (env like TERM, or its terminal-capability detection) and whether it can be told to emit Sixel.
+2. Sixel render-format availability: eat-sixel-render-formats lists preferred render backends; if none is available in this Emacs build, Sixel silently won't display. Test EAT with a known-good sixel image (e.g. img2sixel output) to confirm EAT-side rendering works at all.
+
+Repro: in an EAT session, have Claude Code (or any tool) post an image; observe nothing renders. Next step: identify the emitted escape sequence (capture raw bytes) to confirm protocol.
+
+From the takuzu session, 2026-07-11 — surfaced because the agent kept posting game screenshots the terminal couldn't show.