Branch: refs/heads/4902-image-support
  Home:   https://github.com/tmux/tmux
  Commit: c1d859932d5fc49c2e9c17460824e1a04a46412a
      
https://github.com/tmux/tmux/commit/c1d859932d5fc49c2e9c17460824e1a04a46412a
  Author: Michael Grant <[email protected]>
  Date:   2026-08-21 (Fri, 21 Aug 2026)

  Changed paths:
    A regress/image-floating-content-wipe.sh
    M screen-redraw.c

  Log Message:
  -----------
  screen-redraw: erase only cells a pane owns, not its raw rectangle

image_redraw_start() was called with a pane's full nominal geometry
rather than the cells it actually owns in the current scene. When a
floating pane occluded part of that rectangle, the erase blanked the
floating pane's on-screen content, and the following text redraw
correctly skipped those cells (not owned by this pane), leaving them
blank with nothing to restore them.


  Commit: 0aec6de0486211c0c0658c60a7d88e0a9ae90c2e
      
https://github.com/tmux/tmux/commit/0aec6de0486211c0c0658c60a7d88e0a9ae90c2e
  Author: Michael Grant <[email protected]>
  Date:   2026-08-21 (Fri, 21 Aug 2026)

  Changed paths:
    M regress/image-support.sh

  Log Message:
  -----------
  regress: fix contradictory terminal-features assertions in image-support.sh

Three adjacent blocks shared one 'set -as terminal-features' setting
with contradictory requirements - fallback text, then real SIXEL, then
fallback text again in a single client attach. terminal-features is
only detected at client attach, not live, so this needs detach/reattach
between blocks rather than toggling the option in place.


  Commit: 4b72addf86300ab83122d76c6b9f2d7b40f6dc3e
      
https://github.com/tmux/tmux/commit/4b72addf86300ab83122d76c6b9f2d7b40f6dc3e
  Author: Michael Grant <[email protected]>
  Date:   2026-08-21 (Fri, 21 Aug 2026)

  Changed paths:
    A regress/image-border-status-wipe.sh

  Log Message:
  -----------
  regress: add failing test for border-status redraw bug

window_make_pane_status() gates physical redraw of border-status text on
a logical content diff, not physical damage - if something else disturbs
those cells, the text stays blank because tmux believes nothing changed.
This test currently fails and is expected to keep failing until the
general damage-tracking redraw work lands (see IMAGE-REDRAW-PLAN.md).


  Commit: 0ca50d00aa6a25c2508ff4b9f276f9ea042d0c52
      
https://github.com/tmux/tmux/commit/0ca50d00aa6a25c2508ff4b9f276f9ea042d0c52
  Author: Michael Grant <[email protected]>
  Date:   2026-08-22 (Sat, 22 Aug 2026)

  Changed paths:
    M regress/image-border-status-wipe.sh
    M screen-redraw.c
    M screen-write.c
    M server-client.c
    M tmux.h
    M window.c

  Log Message:
  -----------
  screen-redraw, screen-write, server-client: add damage-rectangle
tracking and composition (temporary duplicate, pending rebase)

Ports the damage-rectangle infrastructure from the redraw-damage-rectangles
branch (github.com/tmux/tmux, based on master) so that this branch's own
image-specific damage reporting (image_redraw_area(), following commits)
has something to report into. This is deliberately a duplicate: once
redraw-damage-rectangles (or whatever form it takes) lands in master, this
branch should rebase onto that and this commit should disappear, along
with the temporary #ifdef ENABLE_IMAGES bridge in redraw_draw_damage_rect()
that image_redraw_start() needs pending that rebase.

Also includes the regress/image-border-status-wipe.sh flip from red to
green - it was written to assert correct behaviour and expected to pass
once this landed.


Compare: https://github.com/tmux/tmux/compare/ec9859b15f19...0ca50d00aa6a

To unsubscribe from these emails, change your notification settings at 
https://github.com/tmux/tmux/settings/notifications

-- 
You received this message because you are subscribed to the Google Groups 
"tmux-git" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion, visit 
https://groups.google.com/d/msgid/tmux-git/tmux/tmux/push/refs/heads/4902-image-support/ec9859-0ca50d%40github.com.

Reply via email to