[Geany] Current Line Colour & Ferite

[Rowan Lewis]

Enrico Tröger wrote:
> On Sun, 08 Oct 2006 00:37:37 +0930, Rowan Lewis
> <rowan at pixelcarnage.net> wrote:
>
>   
>> Hello,
>>
>> I just wanted to point out that currently, changing the
>> "current_line" property in |filetypes.common has no effect. Which is
>> fairly annoying when trying to make a dark on light style ;)
>>     
>
> You have to activate this feature with the third argument. Look at the
> comment from the original filetypes.common:
>
> # background colour of the current line, only the second and third
> # argument is interpreted
> # use the third argument to enable or disable the highlighting of the
> # current line (has to be true/false)
> current_line=0x0;0xf0f0f0;true;false
>
>   
>> Also, here are some updated lines for the Ferite filetype:
>> primary=false null self super true abstract alias and arguments
>> attribute_missing break case class closure conformsToProtocol
>> constructor continue default deliver destructor diliver directive do
>> else extends eval final fix for function global handle if iferr
>> implements include instanceof isa method_missing modifies monitor
>> namespace new or private protected protocol public raise recipient
>> rename return static switch uses using while
>> types=boolean string number array object void XML Unix Sys String
>> Stream Serialize RMI Posix Number Network Math FileSystem Console
>> Array Regexp XSLT docComment=brief class declaration description end
>> example extends function group implements modifies module namespace
>> param protocol return return static type variable warning
>>     
> Thanks.
>
>
> Regards,
> Enrico
>
> --
> Get my GPG key from http://www.uvena.de/pub.key
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geany mailing list
> Geany at uvena.de
> http://uvena.de/cgi-bin/mailman/listinfo/geany
>   
Right, turns out my filetype.common was in the wrong place, my mistake.

Also, Ferite doesn't use try. Its error handling structure is like the
following:
monitor {
    // Code...
} handle (error) {
    // Error...
} else {
    // Else...
}

Else isn't required, so shouldn't be inserted by default.

Thanks, Rowan.