Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Possible style overwrite?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
John Yeung  
View profile   Translate to Translated (View Original)
 More options Jul 10 2012, 11:05 pm
From: John Yeung <gallium.arsen...@gmail.com>
Date: Tue, 10 Jul 2012 23:05:34 -0400
Local: Tues, Jul 10 2012 11:05 pm
Subject: Re: [scite] Possible style overwrite?

> Important thing
> learned is that there is no way for defining custom style for scite without
> doing it by hand for every lexer .properties file separately.

Well, it's true (as far as I know) that you have to override each
properties file separately, but any overrides you do should be done in
your user properties file.  This way you keep them all in one place
and you don't have to redo them if you go to a newer version of SciTE.

I admit it is cumbersome to have a set of overrides for each lexer,
but you only have to do it once.  I haven't made any major changes to
my properties in years, and the only time I have to do it is when I
start using a new language I haven't used before.

Also, if you want to keep the styles more-or-less consistent across
different lexers, use the symbolic names instead of hex codes.  For
example, I've set

# Comment
style.python.1=$(colour.code.comment.line),$(font.comment)
# Number
style.python.2=$(colour.number)
# String
style.python.3=$(colour.string),$(font.monospace)
# Single quoted string
style.python.4=$(style.python.3)
# Keyword
style.python.5=$(colour.keyword)

and so forth.  Similarly, any lexer that I use regularly has its
properties overridden in this manner.  Now I can change the color of
numbers in all the lexers *that I use* by modifying just
$(colour.number), earlier in my user properties file.

I agree that the design could have been more flexible and easier to
customize.  But going back to fix it now would probably be a
tremendous amount of work, and more trouble than it's worth.

John


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.