33

My apologies if Stackoverflow was the incorrect Stackexchange site for this IDE-related question.

I am working on a project, which is shared with Git, on Eclipse Luna. As such, I rely on the EGit plugin for Git integration in the IDE (note that I have installed the latest version of EGit, 3.5). I prefer using dark colour themes in my IDEs, so I am using Moonrise UI and Eclipse Color Themes plugins to enable this behaviour.

It all works fine, my IDE is dark and colours within the toolbars and menu are not abnormal. However, there are still problems with the EGit colouring in my Package Explorer. The main issue is that certain text in the Package Explorer is now coloured black (this is being done on directories and files that have been edited). And this is against a black background. This makes it near impossible to see the text that is being coloured.

I know that I can change this colouring manually by going into Preferences --> General --> Appearance --> Colors And Fonts, select Git, and change all actions resulting in the colour black to be a different colour instead. However, I find this to be a little tedious and I thought that perhaps there is a more intuitive way to have these colours changed dynamically to make more sense against a dark background. I am also having these thoughts because this issue has already been reported as a bug in EGit that should have been fixed by version 3.5.

Any insight into this issue I'm facing is much appreciated.

ecbrodie
  • 11,246
  • 21
  • 71
  • 120

5 Answers5

43

You need to edit the Eclipse Theme. Go to Window -> Preferences -> Appearance > Colors and Fonts. Search by Uncommitted Change (Foreground), edit and choose your preferred color.

Rudge
  • 630
  • 7
  • 7
  • "Ignored resources" is another one with a dark font, so get that one too while you are at it. – Nicholas DiPiazza Jan 08 '19 at 14:06
  • 1
    The MercurialEclipse plugin has similar problems and this solution works as well but you need to browse for "MercurialEclipse". – Adam Gent Aug 08 '19 at 13:49
  • For *MercurialEclipse* (*Eclipse 4.17* with *MercurialEclipse 2.12.0*): `Window -> Preferences -> Appearance -> Colors and Fonts -> MercurialEclipse` **`Changed (Foreground)`** (was `rgb(0,0,0)`) changed to ***rgb( 0, 128, 255 )*** (light blue). Had to `Apply and close` and eventually refresh or reopen the *Project Explorer* view to make it work. – Andreas Covidiot Aug 02 '22 at 08:16
11

I use regular Git which also gave black text. You can completely disable it in Preferences > Appearance > Label Decorations where you uncheck Git.

I don't think it is possible to disable Git text change but keep the '>' changes.

DenBrahe
  • 151
  • 1
  • 9
10

Instead of disabling the feature all-together you can keep Git decorators enabled and modify a few settings. You will still be able to see the theme's correct colors and there are only 2 things you must change:

  1. Go to Preferences -> General -> Appearance -> Colors and Fonts -> Git.
  2. Select "Uncommitted Change (Foreground)".
  3. Set to about 72% white on a black vs white slide bar.
  4. Select "Ignored Resource (Foreground)".
  5. Set to about 72% white on a black vs white slide bar.
  6. Click Apply and Okay.

You should be good to go and will have the freedom to configure whatever colors you wish to show the "Ignored" fields and the "Uncommitted Change" fields.

We are developers here... Not feature killers...

Chad Van De Hey
  • 2,716
  • 3
  • 29
  • 46
3

As long as all the other fonts and colors are to your liking in in Eclipse - go to...

Window -> Preferences -> General -> Appearance -> Label Decorations

Uncheck Git and why not SVN while you're at it.

This should clear everything up for EGit.

You may also find that unchecking other items in this section will clear up other font/color issues you might have.

JxAxMxIxN
  • 1,711
  • 1
  • 17
  • 20
  • This is like killing a fly with dynamite.. You lose uncommited changes indication, one of the most interesting features of EGit, IMO. not worth it.. – Bruno Medeiros Oct 22 '17 at 14:50
-2

Use another tool for git management (like Sourcetree or even the cli git) and disconnect your project by right clicking on it, going to the Team menu and selecting "disconnect" from it. Works fine for me that way, since I'm used to use the cli git.

  • 1
    This has nothing to do with Eclipse as my scm manager. I will often use CLI git or Sourcetree for running my got commands. However, it is common for IDEs to use basic UI features to reflect status of git management. It is for convenience. – ecbrodie May 21 '15 at 02:50
  • Well, the problem you have is a KNOWN BUG on eclipse theme, and I suggested you to disconnect your project on Eclipse only. Since it's a BUG, asking on Stackoverflow how to solve a products BUG won't get any useful answer. – Pablo Santiago Sánchez Apr 26 '17 at 16:18