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

vim colorscheme does render BG colors correctly. Corrupts shell window BG colors. #564

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

Originally created by @OriginalMadProgrammer on GitHub (Feb 17, 2019).

Linux HEINLEIN 4.4.0-17134-Microsoft #523-Microsoft Mon Dec 31 17:49:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Seems related to https://github.com/Microsoft/console/issues/85

Please fill out the below information:

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Microsoft Windows [Version 10.0.17134.590]

  • What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

Each CASE starts with a freshly started shell window.

CASE 1:

vi /etc/passwd
:colorscheme blue
:q

  • What's wrong / what should be happening instead:
    Expected: Background should be entirely blue, unless syntax highlighting changed it.
    Observed: Blue background stops at the end of each line then returns to native black.

    Expected: on exit screen should return to all black background on return to shell.
    Observed: blue background on characters of bottom line that also returns to native black at EOL.
    New blue background under text are for each new line written.

NOTE: repeating the vi command produces a screen with full blue background, as desired..

CASE 2:
https://github.com/GilbertsHub/web-utils/blob/master/cgibinIntercept.sh

vi cgibinIntercept.sh 
:colorscheme blue
:q

Expected: background is all blue.
Observed: in this case background is correctly all blue.

Expected: on exit shell window should return to black background.
Observed: same is with CASE 1 exit.

Originally created by @OriginalMadProgrammer on GitHub (Feb 17, 2019). Linux HEINLEIN 4.4.0-17134-Microsoft #523-Microsoft Mon Dec 31 17:49:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the [console issue tracker](https://github.com/microsoft/console/issues). Seems related to https://github.com/Microsoft/console/issues/85 **Please fill out the below information:** * Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.17134.590] * What you're doing and what's happening: (Copy&paste the full set of _specific_ command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.) Each CASE starts with a freshly started shell window. CASE 1: vi /etc/passwd :colorscheme blue :q * What's wrong / what should be happening instead: Expected: Background should be entirely blue, unless syntax highlighting changed it. Observed: Blue background stops at the end of each line then returns to native black. Expected: on exit screen should return to all black background on return to shell. Observed: blue background on characters of bottom line that also returns to native black at EOL. New blue background under text are for each new line written. NOTE: repeating the vi command produces a screen with full blue background, as desired.. CASE 2: https://github.com/GilbertsHub/web-utils/blob/master/cgibinIntercept.sh vi cgibinIntercept.sh :colorscheme blue :q Expected: background is all blue. Observed: in this case background is correctly all blue. Expected: on exit shell window should return to black background. Observed: same is with CASE 1 exit.
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-Rendering Area-VT Issue-Bug Product-Conhost Resolution-Fix-Available
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#564
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?