Gedit CC Extension

What is gedit?
Gedit is a simple but useful text editor usually found in GNOME-based linux systems.
It allows you choose from a multitude of different coding styles so it is very useful for all sorts of applications!
It also has variable tab widths and gives you the line number.
More information can be found here: https://projects.gnome.org/gedit/

The most important aspect of gedit is that it runs using gtksourceview.
Thus, you can create extensions for gedit to read new languages or add new functionality.
I haven't added any true cc functionality yet, at this point it's simply an extension to highlight definitions inside of cc .ini files

Generally this extension should help you against any things that are misspelled etc...
You can download the extension here:



Installation:
1. Download gedit for windows here
2. Extract the CCGEditv1.rar into ~/gedit/share/gtksourceview-2.0/language-specs/
3. It will ask you if you want to replace the ini.lang that is present, simply overwrite it
4. You should be able to open any cc .ini and it should automatically recognize the file format and set the set language to .ini

If you're having trouble locating the actual executable, it's in ~/gedit/bin/gedit.exe

Here's a screenshot:


Here's what the colours generally mean:
Defining New Objects Eg: AddActor, AddEmission, Etc
A numerical value, coordinate definitions, None, True, False
Object Classes Eg: MOSRotating, MOpixel, Head
Definitions with an object/class as input
Definitions using numbers or boolean values (the bulk of CC coding)
Anything Referencing external resources
Comments

Known issues:
-----------------------------------------------------
- Anytime any of the variables are used in the name or whatnot they get highlighted as well. This is incredibly annoying but I am not sure how to fix them since in other major programming languages there's usually a " " enclosure or something to that effect which could define is a name or something. CC however does not have anything of the sort.

Version History:
-----------------------------------------------------
Version 1.0: Release

Hopefully you guys find this useful.
Let me know if there's anything I missed and feedback/suggestions are appreciated!

Very nice but some of the colors for the color code seem dangerously similar.

Yes but the ones that are similar are colored similar and the ones that are in a different category are colored in a different category of similars categories. That said you will most like never see 2 of the same looking colors on one line.

I considered creating a new colour set but that would require me to add an additional step in setting up gedit.
Gedit uses .xml files with the style schemes within and all of my code is based on default ways of defining a colour that is normally associated with said variable.
This means using "def:comment" will look for the "def:comment" style in whichever style file you are currently using in Gedit, thus, universally compatible.

However, if a lot of people think the colours are much too similar I'll write up a style sheet for specific use with this extension.

This is clever and very thorough, good job putting it together.
Can you treat = as an escape character or something? I've little knowledge of CC ini but I imagine there would be few or no times when you actually use one of the functions after an equals sign right? And even if you did, it'd probably be fine not to highlight it.

The problem with using = as an escape character is that using lines such as AddEmission = MOPixel would not highlight 'MOPIxel'.

Potentially, I could make it so that = after CopyOf, FilePath, PresetName, Description, Etc.. would be an escape character checking CopyOf, etc... before the =.
Not quite sure how I'd go about that though.