starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

sixel inside tmux and ssh workaround #22169

New Issue
Open
opened 2026-01-31 08:05:24 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:05:24 +00:00
Owner
Copy Link

Originally created by @galchinsky on GitHub (Aug 28, 2024).

Windows Terminal version

1.22.240823002-preview

Windows build number

10.0.22631.4037

Other Software

tmux next 3.5 (latest so far 34807388b064 commit built with --enable-sixel)

Steps to reproduce

In WSL2 tab img2sixel logo.png just works, hurray. It also works if I ssh to a remote server from the WSL2 tab.

Then I start tmux and run the same command. It outputs in a fallback mode

$ img2sixel logo.png
SIXEL IMAGE (12x6)
++++++++++++
++++++++++++
++++++++++++
++++++++++++
++++++++++++

Then I (similarly to a suggestion at https://github.com/wez/wezterm/issues/1236)

  • go to a Windows "Command Prompt" tab
  • ssh to WSL2 from there
  • create tmux session and type "img2sixel logo192.png" .

sixel output starts to work, even on a remote server + tmux combination. This is weird, because if it wasn't so, I would think it's a tmux bug. But now it seems something is off with how WSL2 tab works.

Expected Behavior

sixel output inside tmux

Actual Behavior

tmux outputs

SIXEL IMAGE (12x6)
++++++++++++
++++++++++++
++++++++++++
++++++++++++
++++++++++++

but works correctly if ssh to WSL2 from Windows

Originally created by @galchinsky on GitHub (Aug 28, 2024). ### Windows Terminal version 1.22.240823002-preview ### Windows build number 10.0.22631.4037 ### Other Software tmux next 3.5 (latest so far 34807388b064 commit built with --enable-sixel) ### Steps to reproduce In WSL2 tab `img2sixel logo.png` just works, hurray. It also works if I ssh to a remote server from the WSL2 tab. Then I start tmux and run the same command. It outputs in a fallback mode ``` $ img2sixel logo.png SIXEL IMAGE (12x6) ++++++++++++ ++++++++++++ ++++++++++++ ++++++++++++ ++++++++++++ ``` Then I (similarly to a suggestion at https://github.com/wez/wezterm/issues/1236) * go to a Windows "Command Prompt" tab * ssh to WSL2 from there * create tmux session and type "img2sixel logo192.png" . sixel output starts to work, even on a remote server + tmux combination. This is weird, because if it wasn't so, I would think it's a tmux bug. But now it seems something is off with how WSL2 tab works. ### Expected Behavior sixel output inside tmux ### Actual Behavior tmux outputs SIXEL IMAGE (12x6) ++++++++++++ ++++++++++++ ++++++++++++ ++++++++++++ ++++++++++++ but works correctly if ssh to WSL2 from Windows
claunia added the Issue-BugArea-VTNeeds-Tag-FixProduct-Conpty labels 2026-01-31 08:05:25 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-VT Issue-Bug Needs-Tag-Fix Product-Conpty
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22169
Delete Branch "%!s()"

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?