[GH-ISSUE #677] Rendering issue in Wezterm #1333

New issue

Open

opened 2026-03-14 14:27:12 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 14:27:12 +03:00

Owner

Originally created by @Geobert on GitHub (Feb 7, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/677

Describe the bug
2 kinds of issue:

textual rendering is not correct, borders are out of place.
image is not at the correct location neither

To Reproduce
just launch the app with sixel+fzf features

Screenshots

Environment

OS: Windows 11
Application version: 0.20.4
Application features: sixel + fzf
Shell: pwsh

❯ echo $env:TERM
xterm-256color

Originally created by @Geobert on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/677 **Describe the bug** 2 kinds of issue: - textual rendering is not correct, borders are out of place. - image is not at the correct location neither **To Reproduce** just launch the app with sixel+fzf features **Screenshots** ![Image](https://github.com/user-attachments/assets/fc2dd980-20b4-4697-933a-224650ddf436) **Environment** - OS: Windows 11 - Application version: 0.20.4 - Application features: sixel + fzf - Shell: pwsh ``` ❯ echo $env:TERM xterm-256color ```

kerem added the

bug

label

2026-03-14 14:27:12 +03:00

kerem commented

2026-03-14 14:27:24 +03:00

Author

Owner

@Noex98 commented on GitHub (Feb 28, 2025):

Experience the same thing the exact same thing with the borders and image

OS: Windows 11
Version: 0.20.4
Terminal: Wezterm
Features: Sixel
Shell: Nushell

@Noex98 commented on GitHub (Feb 28, 2025): Experience the same thing the exact same thing with the borders and image - OS: Windows 11 - Version: 0.20.4 - Terminal: Wezterm - Features: Sixel - Shell: Nushell

kerem commented

2026-03-14 14:27:29 +03:00

Author

Owner

@Lolmerkat commented on GitHub (May 5, 2025):

This is a Wezterm bug and has been fixed since.
However, the fix is only available on the nightly builds as of now.

@Lolmerkat commented on GitHub (May 5, 2025): This is a Wezterm bug and has been fixed since. However, the fix is only available on the nightly builds as of now.

kerem commented

2026-03-14 14:27:34 +03:00

Author

Owner

@JamesManningR commented on GitHub (Jun 20, 2025):

Should this be closed if it's been fixed?
I use wezterm and don't have this issue.

@JamesManningR commented on GitHub (Jun 20, 2025): Should this be closed if it's been fixed? I use wezterm and don't have this issue.

kerem commented

2026-03-14 14:27:39 +03:00

Author

Owner

@Lolmerkat commented on GitHub (Jun 20, 2025):

It's a Wezterm (stable) bug, nothing to do with the application - so in my opinion yes, it should be closed

@Lolmerkat commented on GitHub (Jun 20, 2025): It's a Wezterm (stable) bug, nothing to do with the application - so in my opinion yes, it should be closed