[Lazarus] The color of special characters in the Source Editor

[Martin]

On 16/09/2011 01:02, Paul Ishenin wrote:
> 15.09.2011 20:03, Martin wrote:
>>> I probably fix it for comment, but comments only.
>
> Comments should stay comments. Space in a commect is not the same as a 
> space in other parts of code.
>
> If I were you I would not implement it at all. The only missing thing 
> for comments is a spell checker.
>
> Even if you intend to implement a highlight for spaces in comments it 
> must differ from the highlight for spaces in code.

Yes, as already figured, a (for example) continues underline 
(comment/string) must not be broken by spaces.

the problem to be solved (which I experienced myself) are "show special 
chars".

I myself used (past tense) to have that on all the time, for #9 
detection. But then every space is a dot. So I set the space foreground 
color, near the background, and all the special chars are faded out.
Only in comments and strings, it looks like hell.

For me personally it might already be solved by show #9 as special char 
only.  (though I actually liked the spaces too)

My current idea is to make the color (forground) alpha adjustable.
Doing so, I can very easily, either:
- add an option to apply it only to code-spaces, or top all-spaces 
(checkbox)
- add a 2nd color attribute for all -none-code-spaces (though having 2 
space colors, well might seem strange)

--------
In order to get the best decision, it would be good to understand as 
much about the different forms of usage that people have for the current 
implementation.

So if you can:
- how to you currently use it
    colors and attibutes of spcace/comment/string
- how might it have affected you?