Neil Hodgson wrote:
> What you want to find is group of settings that can be
> easily set to match a language. Finding the minimal group
> helps people get it working since the more settings used,
> the more likely they'll make a mistake.
Well, my thought would be not to change the number of settings at all,
and simply make statement.indent.filepattern always match only the last
nonwhitespace, noncomment character when a character is specified for
that option (as opposed to when a keyword or keywords are specified).
However, I don't know that many languages, and I would not call myself
an expert in any language, so maybe this idea would mess up lots of
other people.
In case anyone is interested, I went ahead and implemented (just for
myself) my off-the-cuff proposal from before, of explicitly choosing to
only match at EOL by using a special character in the properties file.
I picked the asterisk, which may or may not be a stupid choice, but now
I can specify
statement.indent.$(file.patterns.py)=10 :*
and SciTE will only autoindent the next line if it finds a colon
immediately followed by a CR or LF character (within the first 19
"clumps" of style-10 characters). I believe the behavior is otherwise
unchanged, so any existing properties file should continue to work the
same as it does now.
I would be happy to share my code (modified from the production 1.71
release) with anyone who wants it. It's only a small change, and
perhaps a somewhat kludgy one at that, so I don't know if it's worth
submitting to the project.
John
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
