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

Neovim view doesn't adapt on window resizing #4558

New Issue
Closed
opened 2026-01-30 23:50:35 +00:00 by claunia · 9 comments
claunia commented 2026-01-30 23:50:35 +00:00
Owner
Copy Link

Originally created by @mattiatomeo on GitHub (Oct 20, 2019).

Originally assigned to: @DHowett-MSFT on GitHub.

Environment

Windows build number: 10.0.18362.0
Windows Terminal version: 0.5.2762.0

Neovim version: 0.4.2

Steps to reproduce

Open neovim from the terminal, then change the size of the window.

Expected behavior

I expect that neovim view adapt with the new window size

Actual behavior

If I open neovim and I change the window size, neovim view is extended only respect to the horizontal direction.

resizing-shortcut
resizing-no-shortcut

This issue happens only by using Windows Terminal. If I use Powershell, everything works as expected.

Originally created by @mattiatomeo on GitHub (Oct 20, 2019). Originally assigned to: @DHowett-MSFT on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362.0 Windows Terminal version: 0.5.2762.0 Neovim version: 0.4.2 ``` # Steps to reproduce Open neovim from the terminal, then change the size of the window. # Expected behavior I expect that neovim view adapt with the new window size # Actual behavior If I open neovim and I change the window size, neovim view is extended only respect to the horizontal direction. ![resizing-shortcut](https://media.giphy.com/media/lmw6mwroynSfDR4Je8/giphy.gif) ![resizing-no-shortcut](https://media.giphy.com/media/h3jNcGKjapKBiJsUae/giphy.gif) This issue happens only by using Windows Terminal. If I use Powershell, everything works as expected.
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixNeeds-Attention labels 2026-01-30 23:50:35 +00:00
claunia commented 2026-01-30 23:50:36 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 23, 2019):

This strikes me as being a neovim issue. I wonder how they're checking for resizing events?

Actual normal plain vim works just fine for me. Does it work for you?

@DHowett-MSFT commented on GitHub (Oct 23, 2019): This strikes me as being a neovim issue. I wonder how they're checking for resizing events? Actual normal plain _vim_ works just fine for me. Does it work for you?
claunia commented 2026-01-30 23:50:36 +00:00
Author
Owner
Copy Link

@mattiatomeo commented on GitHub (Oct 23, 2019):

I tried with vim, and resizing works fine.

@mattiatomeo commented on GitHub (Oct 23, 2019): I tried with vim, and resizing works fine.
claunia commented 2026-01-30 23:50:36 +00:00
Author
Owner
Copy Link

@parkovski commented on GitHub (Oct 26, 2019):

I think this is the libuv bug. I patched mine and it works fine - see c71c31816e which I really should send a PR for.

@parkovski commented on GitHub (Oct 26, 2019): I think this is the libuv bug. I patched mine and it works fine - see https://github.com/parkovski/libuv/commit/c71c31816ecf9a1b3b41c2b500b0976aad7aea0b which I really should send a PR for.
claunia commented 2026-01-30 23:50:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 28, 2019):

I'm gonna close this as it seems the issue is upstream. Thanks for investigating @parkovski!

@zadjii-msft commented on GitHub (Oct 28, 2019): I'm gonna close this as it seems the issue is upstream. Thanks for investigating @parkovski!
claunia commented 2026-01-30 23:50:36 +00:00
Author
Owner
Copy Link

@jantari commented on GitHub (Feb 23, 2020):

I am not sure this really is (only) a neovim issue, because it does not happen in conhost, only wt.
If it turns out wt is not innocent in this, I feel like this is a must-fix before v1.0 GA.

See:
animation-smaller2

Windows: 10.0.19569.1000 (Insider Fast)
neovim: 0.4.3
Windows Terminal: 0.9.433.0
@jantari commented on GitHub (Feb 23, 2020): I am not sure this really is (only) a neovim issue, because it does not happen in conhost, only wt. If it turns out wt is not innocent in this, I feel like this is a must-fix before v1.0 GA. See: ![animation-smaller2](https://user-images.githubusercontent.com/25607767/75114749-0853a900-5659-11ea-8fa5-53de7664e8a6.gif) ```yaml Windows: 10.0.19569.1000 (Insider Fast) neovim: 0.4.3 Windows Terminal: 0.9.433.0 ```
claunia commented 2026-01-30 23:50:37 +00:00
Author
Owner
Copy Link

@paulchannelstrip commented on GitHub (Sep 23, 2020):

This should not be closed. I'm having the same issue at the moment. See the screencapture from @jantari

Here's nvim's internal doc on how it gets window-size:
neovim_window-size_doc

@paulchannelstrip commented on GitHub (Sep 23, 2020): This should not be closed. I'm having the same issue at the moment. See the screencapture from @jantari Here's nvim's internal doc on how it gets window-size: ![neovim_window-size_doc](https://user-images.githubusercontent.com/68175317/94065759-6340b080-fda0-11ea-9edc-4f668c067f7b.png)
claunia commented 2026-01-30 23:50:37 +00:00
Author
Owner
Copy Link

@jantari commented on GitHub (Sep 24, 2020):

@npaulcarlson Whether it is a WT issue or not, I'm not qualified to say. But I can give you the tip that it works fine with the 0.5.0 prerelease versions of neovim. I'm using NVIM v0.5.0-558-g6d1404faf specifically right now and this problem is fixed there. You just cannot use 0.4.3 (and I don't know about the recently-released stable 0.4.4 as I haven't tried it)

@jantari commented on GitHub (Sep 24, 2020): @npaulcarlson Whether it is a WT issue or not, I'm not qualified to say. But I can give you the tip that it works fine with the 0.5.0 prerelease versions of neovim. I'm using `NVIM v0.5.0-558-g6d1404faf` specifically right now and this problem is fixed there. You just cannot use 0.4.3 (and I don't know about the recently-released stable 0.4.4 as I haven't tried it)
claunia commented 2026-01-30 23:50:37 +00:00
Author
Owner
Copy Link

@fabiomarreco commented on GitHub (Nov 12, 2020):

@jantari is correct. It works on v0.5.*, but it does not work on 0.4.4

@fabiomarreco commented on GitHub (Nov 12, 2020): @jantari is correct. It works on v0.5.*, but it does not work on 0.4.4
claunia commented 2026-01-30 23:50:37 +00:00
Author
Owner
Copy Link

@bradphelan commented on GitHub (Jun 18, 2021):

Can verify that installing the 0.5 beta fixes the problem

choco install neovim --pre

on windows

@bradphelan commented on GitHub (Jun 18, 2021): Can verify that installing the 0.5 beta fixes the problem ``` choco install neovim --pre ``` on windows
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-Attention Needs-Tag-Fix Needs-Triage Resolution-External
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#4558
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?