starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-09 02:26:45 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Powershell subscript causes tmux display issues #78

New Issue
Open
opened 2026-01-30 21:41:38 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:41:38 +00:00
Owner
Copy Link

Originally created by @bitcrazed on GitHub (Feb 16, 2018).

From @serrearthur on December 7, 2017 21:35

When executing a powershell.exe script inside a tmux session, this will mess the display until the tmux session is closed.

capture
On this picture, the left pane should be filled with text from the output of ls -al, and the right panes are missing part of their borders.

Step to reproduce :

  • Install tmux (tested with tmux 2.6)
  • Launch it (works even without .tmux.conf file)
  • Create a new vertical pane : tmux split-window -h
  • Launch a powershell.exe command : powershell.exe -Help | less
    This will mess up your display : it hides parts of your screen, will not update some data, will copy some text all over your screen, ...

Cases tested :

  • Reproduced with both bash and zsh
  • Reproduced even when redirecting the output of powershell : powershell.exe -Help &>/dev/null
  • Reproduced with various powershell flags : powershell.exe -NoLogo -NoProfile -NonInteractive -OutputFormat Text -Help &>/dev/null
  • Reproduced even without doing tmux split-window -h. However, there are only a few graphical bugs in this case. Spliting the window makes the problem clearer.
  • Windows version : 10.0.17046.1000

Is this a bug ? Is there a workaround ?

Just as a side note, the reason I wanted to execute powershell commands is because I want to retreive the status of NUM_LOCK and CAPS_LOCK, and xset q always return false on WSL. Instead, I used powershell.exe "[console]::NumberLock" and powershell.exe "[console]::CapsLock" to get the real status.

Copied from original issue: Microsoft/WSL#2731

Originally created by @bitcrazed on GitHub (Feb 16, 2018). _From @serrearthur on December 7, 2017 21:35_ When executing a `powershell.exe` script inside a tmux session, this will mess the display until the tmux session is closed. ![capture](https://user-images.githubusercontent.com/4455328/33739467-7b0ce5c6-db9d-11e7-93c6-9aa5b1d2199c.PNG) On this picture, the left pane should be filled with text from the output of `ls -al`, and the right panes are missing part of their borders. Step to reproduce : - Install `tmux` (tested with `tmux 2.6`) - Launch it (works even without `.tmux.conf` file) - Create a new vertical pane : `tmux split-window -h` - Launch a powershell.exe command : `powershell.exe -Help | less` This will mess up your display : it hides parts of your screen, will not update some data, will copy some text all over your screen, ... Cases tested : - Reproduced with both `bash` and `zsh` - Reproduced even when redirecting the output of powershell : `powershell.exe -Help &>/dev/null` - Reproduced with various powershell flags : `powershell.exe -NoLogo -NoProfile -NonInteractive -OutputFormat Text -Help &>/dev/null` - Reproduced even without doing `tmux split-window -h`. However, there are only a few graphical bugs in this case. Spliting the window makes the problem clearer. - Windows version : 10.0.17046.1000 Is this a bug ? Is there a workaround ? --- Just as a side note, the reason I wanted to execute `powershell` commands is because I want to retreive the status of NUM_LOCK and CAPS_LOCK, and `xset q` always return `false` on WSL. Instead, I used `powershell.exe "[console]::NumberLock" ` and `powershell.exe "[console]::CapsLock" ` to get the real status. _Copied from original issue: Microsoft/WSL#2731_
claunia added the Product-ConhostArea-Interop labels 2026-01-30 21:41:38 +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-Interop Product-Conhost
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#78
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?