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

When scrolling vim, text is not displayed properly. #312

New Issue
Open
opened 2026-01-30 21:48:34 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:48:34 +00:00
Owner
Copy Link

Originally created by @toloveru on GitHub (Jul 3, 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)
    Windows Home Insider Preview build 17704.rs_prerelease.180623-1611 (fast ring)

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    When using vim - both on local or SSH remotes and on both Ubuntu 16.04 as well as 18.04 - when scrolling only the last few lines are shown, while the others aren't rendered. When activating mouse support using :set mouse=a and scrolling down a file, only the last 3 lines are rendered. When using the arrow keys to do so, only the last 1 line is shown. Due to this happening in all the distributions that I've tested so far as well as remotes running different ones, I believe that this is an issue in conhost. Also this doesn't happen in my laptop which runs Arch Mate and on which I'm using Terminology, further supporting that the issue may lie in conhost. Lastly I've tested this issue in SUSE Leap 42 on WSL where the issue is occurring as well.
    One thing that I found noteworthy is that this issue doesn't seem to happen in vi while in SSH sessions to other hosts (on WSL Ubuntu it seems to be linked to vim without any straightforward option to install vi). The aforementioned SSH remotes are running Arch Linux with their default vimrc. Another peculiarity is that Ctrl-L (which redraws the shell) makes the rendering happen correctly. Needless to say, having to do that every time when scrolling is a PITA.

  • What's wrong / what should be happening instead:
    The text should be rendered properly and be kept like that during scrolling.

Originally created by @toloveru on GitHub (Jul 3, 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) Windows Home Insider Preview build 17704.rs_prerelease.180623-1611 (fast ring) * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) When using vim - both on local or SSH remotes and on both Ubuntu 16.04 as well as 18.04 - when scrolling only the last few lines are shown, while the others aren't rendered. When activating mouse support using `:set mouse=a` and scrolling down a file, only the last 3 lines are rendered. When using the arrow keys to do so, only the last 1 line is shown. Due to this happening in all the distributions that I've tested so far as well as remotes running different ones, I believe that this is an issue in conhost. Also this doesn't happen in my laptop which runs Arch Mate and on which I'm using Terminology, further supporting that the issue may lie in conhost. Lastly I've tested this issue in SUSE Leap 42 on WSL where the issue is occurring as well. One thing that I found noteworthy is that this issue doesn't seem to happen in vi while in SSH sessions to other hosts (on WSL Ubuntu it seems to be linked to vim without any straightforward option to install vi). The aforementioned SSH remotes are running Arch Linux with their default vimrc. Another peculiarity is that Ctrl-L (which redraws the shell) makes the rendering happen correctly. Needless to say, having to do that every time when scrolling is a PITA. * What's wrong / what should be happening instead: The text should be rendered properly and be kept like that during scrolling.
claunia added the Resolution-Duplicate label 2026-01-30 21:48:34 +00:00
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 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#312
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?