Stephan KçÎper <Stephan.Kaemper / t-online.de> wrote:

>As far as I see, there are several text editor out there which can be
>configuerd with respect to syntax highlighting.
>
>Now, as I like syntax highlighting I'm going to check out some of those
>editos (any suggestions which one is a really good one?).

I also tried a few different editors but didn't find a really good
one.  On Linux, I used emacs but I don't like the lazy syntax coloring
and the default colors a IMHO painful to look at.  At least, it does a
nice job on indenting.  On Windows I tried vi (actually vim) which is
part of the cygwin installation.  I fixed a couple of problems in the
ruby syntax highlighting code and I like the colors and the immediate
coloring, but still - it's a vi.  It also cannot correctly indent and
unindent.  So I'm currently using jedit where I also hacked to syntax
highlighting code.  Unfortunately, it cannot automatically unindent.

>The question is: How should the keywords (and other chars) be grouped?
>Forms of parens... [](){}...
>reserved words
>operators
>symbols

I don't really understand the question.  I like the way vi does the
coloring.  It uses one color (blue I think) for class/def/end, another
color (yellow) for things like if/for/do/end and different colors for
class and instance variables, symbols, reserved words and so on. I
don't care whethere operators are colored special.  However, something
which I still haven't got right is, that "[]=", "nil?" and so on
should be correctly colored as method calls.

bye
-- 
Stefan Matthias Aust \/ Truth Until Paradox