[Geany-devel] Javascript keyword list
Hi, you have a lot of crap in the javascript keyword list. I attached a correct, up-to-date list. (At least I think it's correct and up-to-date). Here it comes: [keywords] # all items must be in one line primary=break case catch const continue delete else eval false finally for function if in try instanceof isFinite isNaN NaN new null return switch this throw true typeof undefined var while with default let secondary=Object Function Array prototype ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Separate color schemes and filetype definitions
I have a suggestion regarding color schemes/filetype definitions. Currently, filetype definitions (keywords, compile-commands, ...) and syntax highlighting color schemes aren't separate, it's one file. This results in problems: 1. if you update filetype defs, there are still lots of old defs going around on the Net (included in custom color schemes) 2. if you switch the color scheme, you lose filetype settings (compile-commands, ...) 3. creating new color schemes is very time-wasting and annoying, because you will do a lot of copy and paste. (to be extended) 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? Regards, Jonas ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [ANNOUNCEMENT] website rework
Hi Lex, Am Dienstag, den 16.02.2010, 15:22 +1100 schrieb Lex Trotman: Hi Dominic, Nice, I like the clean background, but then I run my monitors at medium brightness because I get a lot of white backgrounds, eg PDFs Attached are patches against the HTML. They only change some minor English and punctuation. Thanks very much for the patches. I applied them immediately. :) The only other comment is that if someone is only doing documentation, they really only need to check out trunk/doc/geany.txt not the whole SVN. I added a hint about that, you maybe want to have another look there. :) Regards, Dominic -- Dominic Hopf dma...@googlemail.com http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Separate color schemes and filetype definitions
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 https://geany.svn.sourceforge.net/svnroot/geany/branches/custom-filetypes for that. Regards, Dominic -- Dominic Hopf dma...@googlemail.com http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Separate color schemes and filetype definitions
On 02/16/2010 09:28 PM, Dominic Hopf wrote: I like your suggestions, but I'm actually not sure if they may already are implemented in SVN - maybe in a bit different way. I would like to look at that, but... https://geany.svn.sourceforge.net/svnroot/geany/branches/custom-filetypes ...sourceforge still answers my request. It has been doing that for 2 minutes now. Couldn't you just migrate from that slooow sourceforge and that crappy svn to fast git? I mean, you already have a git mirror. ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
