Is there a way to only color files that have had their git statuses changed and not all parent folders, unless the directory the modified file is in is folded (and color only that folder and not all parents)?
Currently if a file has changed with respect to version control, every folder in the path is also colored, leading to too much color info for my liking:
I'd like everything except for the file someService.ts to be the same color as the models directory.
Also, if possible, all the info on the right (green dots and U) isn't really necessary anymore since the coloring conveys that information, so it's clutter for me. Would it be possible to remove that information and only display the number of errors/warnings in the file?
I have found no built in settings that allows you to set the colors of folders/files individually. It's either all or nothing. To turn the colors on and off, toggle the explorer.decorations.colors setting:
There is a settings to remove the green dots/letters. These are called "badges." To turn them off, toggle the explorer.decorations.badges setting:
This will however also remove the same badges that display the number of errors in a file, etc.
So by default if a change is made, VSCode Source Control sets a blue marker on the file and all directories that contain the changes.
And it also colors the names, which for me in some situations, seems a bit distracting in bigger applications.
Is there a way to customize this, so the Folder and File names do not change color and only the small Markers on the right remain ?
If you use the "explorer.decorations.colors" setting, you can turn off all colors on the text, while still maintaining the "Modified" indicator. This turns off all coloring, but I think really the only coloring I've seen so far comes from Git tracking changes, and if problems are detected in files - those are probably the most common forms of coloring at least.
For example, with "explorer.decorations.colors" set to false,:
You can also set "git.decorations.enabled" to false, but you will lose the indicator as well.
I'm using the default theme. The terminal's colors are impossible to read, make no sense, and are inconsistent. I've tried switching themes but they're terrible in all the themes.
Here's what it looks like in the default. Are you able to read my yellow input against the gray background? And why isn't there a black background everywhere?
I realize there are settings that can manually set the fore/background colors. But I'm thinking something is broken for me because of how screwy the terminal behaves.
For example, here's what I see when I first start the terminal, type a bunch of stuff, backspace to delete half of it, resize the terminal pane, then delete some more. Notice how some of the deleted spaces have yellow and some have gray. Also notice how the area where the CWD would be shown is all black.
Here are the contents of my settings.json file:
{
"window.zoomLevel": 0,
"git.enableSmartCommit": true,
"workbench.startupEditor": "newUntitledFile"
}
What needs fixing, and how?
Edit:
Just to satisfy your curiosity, I added this to my settings.json file:
"workbench.colorCustomizations": {
"terminal.foreground": "#ffffff",
"terminal.background": "#000000"
}
No joy:
There might be something wrong in your console settings, you might want to remove the content of HKCU\Console in your registry. Save it before, obviously, but there shouldn't be any side effect: it'll just be recreated with the default settings.
Okay, so here's a list of all possible settings that you could tweak in your terminal window colorscheme: (source)
"workbench.colorCustomizations": {
"terminal.background":"#1D2021",
"terminal.foreground":"#A89984",
"terminalCursor.background":"#A89984",
"terminalCursor.foreground":"#A89984",
"terminal.ansiBlack":"#1D2021",
"terminal.ansiBlue":"#0D6678",
"terminal.ansiBrightBlack":"#665C54",
"terminal.ansiBrightBlue":"#0D6678",
"terminal.ansiBrightCyan":"#8BA59B",
"terminal.ansiBrightGreen":"#95C085",
"terminal.ansiBrightMagenta":"#8F4673",
"terminal.ansiBrightRed":"#FB543F",
"terminal.ansiBrightWhite":"#FDF4C1",
"terminal.ansiBrightYellow":"#FAC03B",
"terminal.ansiCyan":"#8BA59B",
"terminal.ansiGreen":"#95C085",
"terminal.ansiMagenta":"#8F4673",
"terminal.ansiRed":"#FB543F",
"terminal.ansiWhite":"#A89984",
"terminal.ansiYellow":"#FAC03B"
}
Now for me, the colors of folder names was too bright over an even brighter background color that highlighted them and I couldn't read squat (that's because of my VSCode theme called NightOwl -- :P Sarah) so I thought (wrongly) to change terminal.background and terminal.foreground properties but that refer to the entire rendered window of the terminal.
Because these properties are actually named after Ansi Escape Codes, what I was actually looking for were these properties: terminal.ansiBlue for folder name text color and terminal.ansiGreen for folder name background highlight color.
As soon as I tweaked those, my terminal was good to go.
The way to do it is to just set all these settings and start removing or changing them to see which is which for your preference. K Thx Bye
Also beware that terminal.ansiGreen is used by git diff as a color to show additions.
On March 8th 2022 the default value for the integrated terminal "minimum contrast ratio" was updated from 1 (no effect) to 4.5 (minimal effect). Depending on your color settings and what is being displayed, this can cause your integrated terminal foreground colors to be wrong.
To disable this feature, override the default in your own settings.json file:
"terminal.integrated.minimumContrastRatio": 1
There are two solutions. Xavier's solution works, and mklement0's comment was also correct.
Solution #1
Do what Xavier said (and upvote his answer).
But, if you don't want to mess up registry settings (or if, like me, you have lots of registry settings nestled under the HKCU\Console root), then...
Solution #2
Get Windows 10 build number 18309 (or newer)
Join the Windows Insider Program
Make sure you're on a "ring" that includes a new-enough build. For me at this moment that meant joining the "fast" ring
Wait forever for updates to finish installing
Add "terminal.integrated.windowsEnableConpty": true to your settings.json
Restart terminals
Upvote mklement0's comment
...
Profit!
I am new to VS Code (and I'm trying to better my PowerShell skills) and have/had this same problem. Deleting all the Reg keys cited above related to colors seemed to fix it, but I believe the root problem is that VS Code seems to be trying to honor the color scheme set up outside the VS Code Terminal itself, from the shell. Really annoying and I'm not sure how to separate the two.
I had setup a blue background/yellow font scheme in PS prior to installing VS Code. That was the same color scheme the terminal in VS Code was displaying directly around the text.
I have just started to use Github and have been doing some tests with Gist, I notice beside each revision there are little green and red dots of varying amounts. Does anyone know what they are?
The following image, for example, is captured from this gist.
Those red and green dots represent insertions and deletions in the revision, respectively. There is something similar associated with commits on GitHub (actually, you see the same information when committing in Git), except there you can hover the mouse pointer over the dots and get more information. For example, when hovering over the colored squares in this commit you can see the number of additions and deletions.
I'm trying to find a legend that can help explain the different colors NetBeans uses to describe the state of a file.
Some of my file colors are:
Grey
Blue
Green
Any others I have yet to discover
If it helps, I'm using Netbeans 6.7 with CVS. What are these colors?
Green means new.
Blue means modified.
Grey means ignored and/or deleted. (Documentation contradicts the tooltip hint!)
If you go into the View menu, you can turn on Show Versioning Labels. That will put text next to each file explaining its state (and what each color represents).
Image from Netbeans.org
Using the online help and searching for icon/icons and or badge/badges should give you the information you want.
Alternatively take a look at BadgedIcons which at least explains some of the colors and icons (e.g. for version control)