[Geany-devel] Separate color schemes and filetype definitions

Dominic Hopf dmaphy at xxxxx
Tue Feb 16 20:28:24 UTC 2010

Am Dienstag, den 16.02.2010, 14:03 +0100 schrieb Jonas H.:
> My suggestion is: Separate filetype definitions and color schemes. For 
> example, think of two directories, "colorschemes" and "filedefs". A 
> filedef file contains stuff like a keyword list and so on. A color 
> scheme file contains nothing more but kinda 
> keyword-type-color-assignment, such as
>    primary = #somecolor
> Furthermore I would implement something like inheritance, escpecially 
> for filedefs. Let me explain what I mean by 'inheritance' in that case:
> You have default filedefs in /usr/share/geany/fildefs (or whatever). If 
> a custom filedef is given in .config/geany/filedefs (or whatever), all 
> 'keys' given in that custom file will be overriden. Advantage of this 
> is: The custom files don't have to be a 1:1 copy, but only some kind of 
> 'override-file'.
> Advantage of this is: You can have custom settings for example for 
> compile commands, but still can go with the current up-to-date keyword 
> list (delivered with Geany).
> What do you think?

Hi Jonas,
welcome to the Geany development list. :)

I like your suggestions, but I'm actually not sure if they may already
are implemented in SVN - maybe in a bit different way.

The filetype definition system is under rework at the present. I think
some of the problems you mentioned may already be solved there. It is
developed in a separate branch, but you can follow the development if
you like. Check out


for that.


Dominic Hopf <dmaphy at googlemail.com>


Key Fingerprint:
A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.geany.org/pipermail/devel/attachments/20100216/93489cde/attachment.pgp>

More information about the Devel mailing list