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 ;)
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, Rowan Lewis. |
On Sun, 08 Oct 2006 00:37:37 +0930, Rowan Lewis rowan@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
Enrico Tröger wrote:
On Sun, 08 Oct 2006 00:37:37 +0930, Rowan Lewis rowan@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@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.
On Sun, 08 Oct 2006 14:40:36 +0930, Rowan Lewis rowan@pixelcarnage.net wrote:
Enrico Tröger wrote:
On Sun, 08 Oct 2006 00:37:37 +0930, Rowan Lewis rowan@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:
[...]
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... }
monitor? I had a look at the Ferite documentation and found only iferr { /* some code that might go wronf */ } fix { /* Tidy up! */ } else { /* If we have no error, lets do some different cleaning up */ } for exception handling. I'll add iferr, but what's with monitor?
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
Enrico Tröger wrote:
On Sun, 08 Oct 2006 14:40:36 +0930, Rowan Lewis rowan@pixelcarnage.net wrote:
Enrico Tröger wrote:
On Sun, 08 Oct 2006 00:37:37 +0930, Rowan Lewis rowan@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:
[...]
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... }
monitor? I had a look at the Ferite documentation and found only iferr { /* some code that might go wronf */ } fix { /* Tidy up! */ } else { /* If we have no error, lets do some different cleaning up */ } for exception handling. I'll add iferr, but what's with monitor?
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
Geany mailing list Geany@uvena.de http://uvena.de/cgi-bin/mailman/listinfo/geany
Hey,
The keywords where recently changed from 'iferr' and 'fix', the next release will use 'monitor' and 'handle'.
Also, a question about the current line style: Is it possible to change that for a specific file type? Because I'm working on a dark style for Ferite, but the current line style doesn't work for it, so when I go and change it globaly, it then doesn't work on any other style.
Thanks, Rowan.
On Mon, 09 Oct 2006 10:18:41 +0930, Rowan Lewis rowan@pixelcarnage.net wrote:
Hey,
The keywords where recently changed from 'iferr' and 'fix', the next release will use 'monitor' and 'handle'.
Ok, Geany now supports both.
Also, a question about the current line style: Is it possible to change that for a specific file type? Because I'm working on a dark style for Ferite, but the current line style doesn't work for it, so when I go and change it globaly, it then doesn't work on any other style.
No sorry. This isn't possible at the moment.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key