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

stdout/stderr buffer in PowerShell seems to override content on split panes in tmux. #267

New Issue
Closed
opened 2026-01-30 21:47:20 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 21:47:20 +00:00
Owner
Copy Link

Originally created by @toloveru on GitHub (May 20, 2018).

This bug-tracker is monitored by Windows Console development team and other technical types. We like detail!

If you have a feature request, please post to the UserVoice.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Microsoft Windows [Version 10.0.16299.431]

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    In WSL Bash, I opened tmux and split it up into 4 panes (2x2 configuration). Next, I executed powershell.exe in the top right window, which successfully brought me into a PowerShell. When executing "ls" some of the stdout (or whatever the equivalent in PowerShell is) is printed in the top left pane, where a completely unrelated SSH session to my Arch Linux laptop was ongoing. This seems to me like some of the content (seemingly the string "Mode LastWriteTime Length Name") is hardcoded to start at terminal window column 0 - rather than whatever tmux has decided it should start at.
    It does however seem to disappear whenever I click on the top left pane, and show the running SSH session again.
    powershell

  • What's wrong / what should be happening instead:
    The PowerShell pane should cooperate nicely with WSL Bash and its terminal window border allocations, instead of printing to another tmux pane that it shouldn't even be permitted access to.

Originally created by @toloveru on GitHub (May 20, 2018). This bug-tracker is monitored by Windows Console development team and other technical types. **We like detail!** If you have a feature request, please post to [the UserVoice](https://wpdev.uservoice.com/forums/266908). > **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible * Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.16299.431] * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) In WSL Bash, I opened tmux and split it up into 4 panes (2x2 configuration). Next, I executed powershell.exe in the top right window, which successfully brought me into a PowerShell. When executing "ls" some of the stdout (or whatever the equivalent in PowerShell is) is printed in the top left pane, where a completely unrelated SSH session to my Arch Linux laptop was ongoing. This seems to me like some of the content (seemingly the string "Mode LastWriteTime Length Name") is hardcoded to start at terminal window column 0 - rather than whatever tmux has decided it should start at. It does however seem to disappear whenever I click on the top left pane, and show the running SSH session again. ![powershell](https://user-images.githubusercontent.com/19938179/40279226-e7bdb908-5c3e-11e8-90ba-19c35bc604ff.png) * What's wrong / what should be happening instead: The PowerShell pane should cooperate nicely with WSL Bash and its terminal window border allocations, instead of printing to another tmux pane that it shouldn't even be permitted access to.
claunia added the Resolution-Fix-AvailableResolution-DuplicateArea-Interop labels 2026-01-30 21:47:20 +00:00
claunia commented 2026-01-30 21:47:21 +00:00
Author
Owner
Copy Link

@toloveru commented on GitHub (May 21, 2018):

This may have been just an issue in that particular shell where some of the variables were borked or something like that. I've just tried to reproduce the same environment as above in a new Ubuntu window, and the issue was gone. Apologies for jumping to conclusions too quickly.

@toloveru commented on GitHub (May 21, 2018): This may have been just an issue in that particular shell where some of the variables were borked or something like that. I've just tried to reproduce the same environment as above in a new Ubuntu window, and the issue was gone. Apologies for jumping to conclusions too quickly.
claunia commented 2026-01-30 21:47:21 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 21, 2018):

That's alright. Thank you for cleaning it up.

@miniksa commented on GitHub (May 21, 2018): That's alright. Thank you for cleaning it up.
claunia commented 2026-01-30 21:47:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 21, 2018):

Oh this is a known issue with interop scenarios on April Creator's Update and earlier. Unless the application is just writing raw text, it'll act REALLY poorly when run on interop.

Fortunately that's all fixed in newer builds! See #57 for details. Anything above 17618 will work like a charm :)

@zadjii-msft commented on GitHub (May 21, 2018): Oh this is a known issue with interop scenarios on April Creator's Update and earlier. Unless the application is just writing raw text, it'll act REALLY poorly when run on interop. Fortunately that's all fixed in newer builds! See #57 for details. Anything above 17618 will work like a charm :)
claunia commented 2026-01-30 21:47:22 +00:00
Author
Owner
Copy Link

@toloveru commented on GitHub (May 21, 2018):

@zadjii-msft That's great to hear. Not sure why I'm not on that build yet, as it seems to have been released in the stable channel already. Perhaps something like SpyBot has interfered with the updater. Guess I'll have to reinstall Windows to get on this build and get the patches. Thanks for the clarification!

@toloveru commented on GitHub (May 21, 2018): @zadjii-msft That's great to hear. Not sure why I'm not on that build yet, as it seems to have been released in the stable channel already. Perhaps something like SpyBot has interfered with the updater. Guess I'll have to reinstall Windows to get on this build and get the patches. Thanks for the clarification!
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 Resolution-Duplicate Resolution-Fix-Available
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#267
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?