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

Bug Report #1446

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

Originally created by @dgilmour77 on GitHub (May 31, 2019).

Environment

Windows build number: Version 10.0.18362.116
Windows Terminal version (if applicable): 

Any other software?

1. Ubuntu/WSL:
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

2. VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 10 2018 21:31:58)
Included patches: 1-1453
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by pkg-vim-maintainers@lists.alioth.debian.org

Note: problem appeared after installing May 2019 Windows update

Steps to reproduce

  1. Open Ubuntu terminal by clicking on Ubuntu icon.
  2. Set terminal colors via preferences dialog to background gray, text black
  3. Open a text file with vim:
  4. Scroll down a screen or two
  5. Navigate up with cursor until it causes upward scrolling
  6. Observe background color of repainted area behind text at top of screen

Also:
Occasionally happens when scrolling downward with rapid cursor down keystrokes at the bottom of the screen

Expected behavior

Background color should be uniform

Actual behavior

Background fills with black background, not the gray background that was set in preferences.

scroll problem
The color is temporarily corrected by pressing Control-L, forcing a repaint.

I understand this seems similar to other reported bugs, but workarounds suggested elsewhere have no effect, including:

:set t_ut=""/t_ut=y
:set lazyredraw/nolazyredraw
:set ttyfast/nottyfast

Loading other vim color schemes, disabling .bashrc, did not help. Neovim shows the same problem. I can find no workaround that allows me to use a light grey background and edit files.

Originally created by @dgilmour77 on GitHub (May 31, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Version 10.0.18362.116 Windows Terminal version (if applicable): Any other software? 1. Ubuntu/WSL: Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic 2. VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 10 2018 21:31:58) Included patches: 1-1453 Modified by pkg-vim-maintainers@lists.alioth.debian.org Compiled by pkg-vim-maintainers@lists.alioth.debian.org Note: problem appeared after installing May 2019 Windows update ``` # Steps to reproduce 1. Open Ubuntu terminal by clicking on Ubuntu icon. 2. Set terminal colors via preferences dialog to background gray, text black 3. Open a text file with vim: 4. Scroll down a screen or two 5. Navigate up with cursor until it causes upward scrolling 6. Observe background color of repainted area behind text at top of screen Also: Occasionally happens when scrolling downward with rapid cursor down keystrokes at the bottom of the screen <!-- A description of how to trigger this bug. --> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Background color should be uniform # Actual behavior <!-- What's actually happening? --> Background fills with black background, not the gray background that was set in preferences. ![scroll problem](https://user-images.githubusercontent.com/6298982/58718411-4b127a00-8382-11e9-9757-9976bd7b6d76.jpg) The color is temporarily corrected by pressing Control-L, forcing a repaint. I understand this seems similar to other reported bugs, but workarounds suggested elsewhere have no effect, including: `:set t_ut=""/t_ut=y` `:set lazyredraw/nolazyredraw` `:set ttyfast/nottyfast` Loading other vim color schemes, disabling .bashrc, did not help. Neovim shows the same problem. I can find no workaround that allows me to use a light grey background and edit files.
claunia added the Product-ConhostIssue-BugArea-VTResolution-Duplicate labels 2026-01-30 22:27:27 +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 Area-VT Issue-Bug Product-Conhost 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#1446
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?