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

After quitting vim and resizing the wt, terminal still shows vim interface #17581

New Issue
Closed
opened 2026-01-31 05:46:33 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 05:46:33 +00:00
Owner
Copy Link

Originally created by @leimath on GitHub (May 26, 2022).

Windows Terminal version

Terminal (Unpackaged) Version: 1.13.220523001

Windows build number

10.0.19044.0

Other Software

Name : vim
Description : A highly configurable text editor for efficiently creating and
changing any kind of text. (tux build)
Version : 8.2.5016

Steps to reproduce

  1. [Optional] Disable scrollbar in settings (There is a issue with scroll bar already. Disabling the scroll bar mitigates the issue.)
  2. Start Windows Terminal again in a smaller window size (Columns - 83 * Rows - 31 for me).
  3. Spam a bunch of commands/errors to create some text before vim is started.
  4. Type vim.
  5. Press aor i to get int insert mode. Spam a bunch of text in subsequent lines.
  6. Make Windows Terminal maximized (Maximize button in top right corner) or full screen (Alt + Enter)
  7. Quit vim with :q!
  8. See the bottom of windows terminal
  9. Write some commands to see more glitches happen!

Note: If exited vim with :q! before maximizing (Step: 5) then the entire screen text are in diagonals causing a rendering glitch when maximized after quitting vim. As shown below:

  • I can list the scroll bar issue later on.

Expected Behavior

Should quit normally without causing any interference in the top shell.

Actual Behavior

Glitches on entering commands post maximized resize. Vim lines in the shell. See the image attached here:

Ignore the text errors above vim, they are just spam text.

Originally created by @leimath on GitHub (May 26, 2022). ### Windows Terminal version Terminal (Unpackaged) Version: 1.13.220523001 ### Windows build number 10.0.19044.0 ### Other Software Name : vim Description : A highly configurable text editor for efficiently creating and changing any kind of text. (tux build) Version : 8.2.5016 ### Steps to reproduce 0. [Optional] Disable scrollbar in settings (There is a issue with scroll bar already. Disabling the scroll bar mitigates the issue.) 1. Start Windows Terminal again in a smaller window size (Columns - 83 * Rows - 31 for me). 2. Spam a bunch of commands/errors to create some text before vim is started. 3. Type `vim`. 4. Press `a`or `i` to get int insert mode. Spam a bunch of text in subsequent lines. 5. Make Windows Terminal maximized (`Maximize` button in top right corner) or full screen (`Alt` + `Enter`) 6. Quit vim with `:q!` 7. See the bottom of windows terminal 8. Write some commands to see more glitches happen! Note: If exited vim with `:q!` before maximizing (Step: 5) then the entire screen text are in diagonals causing a rendering glitch when maximized after quitting vim. As shown below: <img src="https://user-images.githubusercontent.com/96306150/170454160-be39a461-0c85-4e6f-b8e6-2dab05f363b3.png" width="650" height="379" /> * I can list the scroll bar issue later on. ### Expected Behavior Should quit normally without causing any interference in the top shell. ### Actual Behavior Glitches on entering commands post maximized resize. Vim lines in the shell. See the image attached here: <img src="https://user-images.githubusercontent.com/96306150/170452814-a43bd240-83ed-44d2-b1f5-cd99f1b5d66b.png" width="650" height="379" /> Ignore the text errors above `vim`, they are just spam text.
claunia added the Issue-BugResolution-DuplicateProduct-Conpty labels 2026-01-31 05:46:33 +00:00
claunia commented 2026-01-31 05:46:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 26, 2022):

I believe this is fixed in 1.14 Preview, can you try that build out and confirm for me/?

@zadjii-msft commented on GitHub (May 26, 2022): I believe this is fixed in [1.14 Preview](https://github.com/microsoft/terminal/releases/tag/v1.14.1432.0), can you try that build out and confirm for me/?
claunia commented 2026-01-31 05:46:35 +00:00
Author
Owner
Copy Link

@leimath commented on GitHub (May 26, 2022):

I believe this is fixed in 1.14 Preview, can you try that build out and confirm for me/?

Not fixed as seen below. I can also replicate the issue mentioned in note as well in this preview version (Didn't add the image here however).

Terminal version: Windows Terminal Preview Version: 1.14.1432.0

Resizing it again gives this:

@leimath commented on GitHub (May 26, 2022): > I believe this is fixed in [1.14 Preview](https://github.com/microsoft/terminal/releases/tag/v1.14.1432.0), can you try that build out and confirm for me/? Not fixed as seen below. I can also replicate the issue mentioned in note as well in this preview version (Didn't add the image here however). <img src="https://user-images.githubusercontent.com/96306150/170525312-e449977a-938e-4ad9-8821-e7d806c58afb.png" width="650" height="379" /> Terminal version: Windows Terminal Preview Version: 1.14.1432.0 Resizing it again gives this: <img src="https://user-images.githubusercontent.com/96306150/170525776-511c8ce4-59c3-4868-b7bd-37309e977f4a.png" width="650" height="379" />
claunia commented 2026-01-31 05:46:35 +00:00
Author
Owner
Copy Link

@leimath commented on GitHub (May 26, 2022):

Here is the scrollbar issue https://github.com/vim/vim/issues/10419#issuecomment-1126716761 for vim and https://github.com/helix-editor/helix/issues/2466 a similar issue for the helix editor that I created.

Sorry if I am not allowed to add issues of other repos but I am not sure on which repo to put them hence adding them here. I can make a separate issue if this is not the right thread.

@leimath commented on GitHub (May 26, 2022): Here is the scrollbar issue https://github.com/vim/vim/issues/10419#issuecomment-1126716761 for vim and https://github.com/helix-editor/helix/issues/2466 a similar issue for the `helix` editor that I created. Sorry if I am not allowed to add issues of other repos but I am not sure on which repo to put them hence adding them here. I can make a separate issue if this is not the right thread.
claunia commented 2026-01-31 05:46:35 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 26, 2022):

@zadjii-msft I may be misremembering, but doesn't the Windows version of VIM use console APIs rather than VT sequences? If that's the case, it probably wouldn't be using the alt buffer, so your new alt buffer support wouldn't help here. My guess is this is possibly a form of the exact wrap bug (#3088, see also #9982).

@j4james commented on GitHub (May 26, 2022): @zadjii-msft I may be misremembering, but doesn't the Windows version of VIM use console APIs rather than VT sequences? If that's the case, it probably wouldn't be using the alt buffer, so your new alt buffer support wouldn't help here. My guess is this is possibly a form of the exact wrap bug (#3088, see also #9982).
claunia commented 2026-01-31 05:46:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 26, 2022):

Ah, yea, I shoulda known better. Yea Windows vim definitely doesn't use the alt buffer, so 1.14 won't fix this. This might also be #202. Surprised that @DHowett isn't more bothered by this (as our resident vim.exe user)

@zadjii-msft commented on GitHub (May 26, 2022): Ah, yea, I shoulda known better. Yea Windows vim definitely doesn't use the alt buffer, so 1.14 won't fix this. This might also be #202. Surprised that @DHowett isn't more bothered by this (as our resident vim.exe user)
claunia commented 2026-01-31 05:46:36 +00:00
Author
Owner
Copy Link

@Vidzhel commented on GitHub (Jun 18, 2022):

You may try this, don't know if it'll help
https://github.com/microsoft/terminal/issues/1940#issuecomment-1159494480

@Vidzhel commented on GitHub (Jun 18, 2022): You may try this, don't know if it'll help https://github.com/microsoft/terminal/issues/1940#issuecomment-1159494480
claunia commented 2026-01-31 05:46:36 +00:00
Author
Owner
Copy Link

@leimath commented on GitHub (Jun 19, 2022):

You may try this, don't know if it'll help #1940 (comment)

Nope, didn't help. I can still repro.

@leimath commented on GitHub (Jun 19, 2022): > You may try this, don't know if it'll help [#1940 (comment)](https://github.com/microsoft/terminal/issues/1940#issuecomment-1159494480) Nope, didn't help. I can still repro.
claunia commented 2026-01-31 05:46:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 20, 2022):

Actually yea, we do have an older issue that's tracking this. This might date all the way back to #202, but it definitely is a /dup of #11147. Let's at least sort of try to consolidate some discussion. Thanks!

@zadjii-msft commented on GitHub (Jun 20, 2022): Actually yea, we do have an older issue that's tracking this. This might date all the way back to #202, but it definitely is a /dup of #11147. Let's at least sort of try to consolidate some discussion. Thanks!
claunia commented 2026-01-31 05:46:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 20, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 20, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Issue-Bug Product-Conpty 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#17581
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?