starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-04-17 11:41:04 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Neovim/tmux rendering glitches after resize #2020

New Issue
Closed
opened 2026-01-30 22:44:38 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 22:44:38 +00:00
Owner
Copy Link

Originally created by @parkovski on GitHub (Jun 23, 2019).

Environment

  • Windows 10.0.18362.175
  • tmux
  • Neovim 0.3.7

Steps to reproduce

Open Neovim (Windows version) inside of tmux and resize the window. If it's not glitching yet, try scrolling around with Ctrl-D/Ctrl-U. Making the window smaller seems to be ok sometimes, but I see glitches if I maximize, restore, resize the window to be larger, or resize a tmux pane. Interestingly, regular vim has problems with maximize/restore, but not resizing by dragging the window edge. I think there is a separate bug there but I'll keep that to a separate issue.

Now for the really strange part. Open a second console window. Tmux and neovim are fixed now. Resize the first window to make it glitchy again, and then resize the second window. Fixed again.

Somehow resizing a regular console window makes unrelated PTY buffers set the correct size.

Expected behavior

For one, resizing should not make programs glitchy, but I certainly didn't expect the sort of "fix" I found either.

Actual behavior

Probably better to just show what's going on.

Originally created by @parkovski on GitHub (Jun 23, 2019). # Environment - Windows 10.0.18362.175 - tmux - Neovim 0.3.7 # Steps to reproduce Open Neovim (Windows version) inside of tmux and resize the window. If it's not glitching yet, try scrolling around with Ctrl-D/Ctrl-U. Making the window smaller seems to be ok sometimes, but I see glitches if I maximize, restore, resize the window to be larger, or resize a tmux pane. Interestingly, regular vim has problems with maximize/restore, but not resizing by dragging the window edge. I think there is a separate bug there but I'll keep that to a separate issue. Now for the really strange part. Open a second console window. Tmux and neovim are fixed now. Resize the first window to make it glitchy again, and then resize the second window. Fixed again. Somehow resizing a regular console window makes unrelated PTY buffers set the correct size. # Expected behavior For one, resizing should not make programs glitchy, but I certainly didn't expect the sort of "fix" I found either. # Actual behavior [Probably better to just show what's going on.](https://vimeo.com/343970593)
claunia added the Needs-Tag-FixResolution-Duplicate labels 2026-01-30 22:44:38 +00:00
claunia commented 2026-01-30 22:44:40 +00:00
Author
Owner
Copy Link

@ibuioli commented on GitHub (Jun 24, 2019):

This is a common error on Terminals that working on Windows and the WSL (Hyper has the same bugs). However it must be fixed. This happend on tmux, vim, neovim and even nano. Here is a screenshot of Nano, when resize Terminal to fullscreen and then window size again:

nano_on_wt

The "bottom tools" broken, and the format of space is incorrect.

@ibuioli commented on GitHub (Jun 24, 2019): This is a common error on Terminals that working on Windows and the WSL (Hyper has the same bugs). However it must be fixed. This happend on tmux, vim, neovim and even nano. Here is a screenshot of Nano, when resize Terminal to fullscreen and then window size again: ![nano_on_wt](https://user-images.githubusercontent.com/7343538/60036023-a0d9f980-9684-11e9-8744-ef40d6841eb3.png) The "bottom tools" broken, and the format of space is incorrect.
claunia commented 2026-01-30 22:44:40 +00:00
Author
Owner
Copy Link

@andres-pcg commented on GitHub (Jun 25, 2019):

This same behavior also happens when using powershell, windows terminal, or cmd to connect through ssh to any linux like enviroment and trying to edit a file using nano, vi, vim or any other editor. git-bash handles this properly. It would be great if we can have this messy issue fix.

@andres-pcg commented on GitHub (Jun 25, 2019): This same behavior also happens when using powershell, windows terminal, or cmd to connect through ssh to any linux like enviroment and trying to edit a file using nano, vi, vim or any other editor. git-bash handles this properly. It would be great if we can have this messy issue fix.
claunia commented 2026-01-30 22:44:40 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

Using #1465 as the main issue tracking resize.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): Using #1465 as the main issue tracking resize.
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 Needs-Tag-Fix Resolution-Duplicate
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#2020
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?