feat(tui): image rendering — sixel backend via img2sixel #57
No reviewers
Labels
No labels
area:agents
area:ai
area:config
area:dashboard
area:design
area:design-review
area:devtools
area:entities
area:gallery
area:generate
area:image
area:infra
area:meta
area:model-browser
area:navigation
area:presets
area:security
area:sessions
area:settings
area:sharing
area:test
area:ux
area:webhook
area:workdir
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/loom!57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tui/sixel-13"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Third of four image backends. Shells out to
img2sixel(from libsixel) rather than taking a Rust build-time sixel dep. Stacks on #56. Closes charles/loom#13.What's in
image::sixel::SixelRendererimplementingImageRendererSixelRenderer::detect()returnsErr(SixelNotFound)whenimg2sixelisn't on$PATHrect.width * 10 × rect.height * 20pixels (default monospace cell ratio); caches payloads under the same(source, w, h)key semantics as KittyTests (2 new, 55 total)
detect()returnsErrwhen$PATHis clearedNotes
sixel/libsixel-sys— keeps build portable and avoids C headers. Terminals that speak sixel invariably have libsixel'simg2sixelcommand availablechafa::which_bin_publicexposes the$PATHwalker so this module and future detect code don't duplicate the traversal