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

Bottom lines of terminal display blocked off after closing vim #12505

New Issue
Closed
opened 2026-01-31 03:17:24 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:17:24 +00:00
Owner
Copy Link

Originally created by @noncomputable on GitHub (Feb 11, 2021).

Environment

Windows build number: Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): Preview
Profile: PowerShell

Any other software?

Steps to reproduce

  1. Open a file with vim: vim file.txt
  2. Close it: :q
  3. Enter any input to the terminal

Expected behavior

The terminal input prompt should appear on the line after vim was entered, and the next line after that should be the output to your input. Any lines after that should be blank.

Actual behavior

Your input is copied to the bottom line of the terminal, and the output is printed on the bottom lines before it. Then the new terminal input prompt appears on the line above the output. If I open any other program, these bottom lines are still blocked off, e.g. after opening a file with vim, the bottom lines of the screen will be the output of my last terminal command followed by the input I last gave to the terminal.

For example, running [Environment]::OSVersion (top line), fills the bottom as follows:
image

If I run clear, the bottom clears but is still unusable, and my next input/output into the terminal is again copied to those bottom lines.

Originally created by @noncomputable on GitHub (Feb 11, 2021). # Environment ```none Windows build number: Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal version (if applicable): Preview Profile: PowerShell Any other software? ``` # Steps to reproduce 1. Open a file with vim: `vim file.txt` 2. Close it: `:q` 3. Enter any input to the terminal # Expected behavior The terminal input prompt should appear on the line after `vim` was entered, and the next line after that should be the output to your input. Any lines after that should be blank. # Actual behavior Your input is copied to the bottom line of the terminal, and the output is printed on the bottom lines before it. Then the new terminal input prompt appears on the line above the output. If I open any other program, these bottom lines are still blocked off, e.g. after opening a file with vim, the bottom lines of the screen will be the output of my last terminal command followed by the input I last gave to the terminal. For example, running `[Environment]::OSVersion` (top line), fills the bottom as follows: ![image](https://user-images.githubusercontent.com/12204924/107599906-1dba3e00-6bf0-11eb-8496-74c1be08a4d8.png) If I run `clear`, the bottom clears but is still unusable, and my next input/output into the terminal is again copied to those bottom lines.
claunia commented 2026-01-31 03:17:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 11, 2021):

Do you have any set lines or set columns directives in your vimrc?

@DHowett commented on GitHub (Feb 11, 2021): Do you have any `set lines` or `set columns` directives in your vimrc?
claunia commented 2026-01-31 03:17:25 +00:00
Author
Owner
Copy Link

@noncomputable commented on GitHub (Feb 12, 2021):

Do you have any set lines or set columns directives in your vimrc?

Nope

@noncomputable commented on GitHub (Feb 12, 2021): > > > Do you have any `set lines` or `set columns` directives in your vimrc? Nope
claunia commented 2026-01-31 03:17:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 2, 2021):

Sorry for the delay here.

What version of Vim are you using? Does this still reproduce with the latest Preview?

@DHowett commented on GitHub (Jul 2, 2021): Sorry for the delay here. What version of Vim are you using? Does this still reproduce with the latest Preview?
claunia commented 2026-01-31 03:17:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 6, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 6, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#12505
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?