Howard Jess:
1. Is .SciteUser.properties the correct place for file.patterns and
command.compile definitions? If I want to deliver this to other
users, is it OK to put it in SciTEGlobal.properties?
The user properties file is the correct place to put your own
settings. Global properties and the files it includes should be left
as they are distributed so that a new version can be inserted without
undoing any of your changes. If you are prepared to perform the extra
work of maintaining your own global properties file for redistribution
then that's OK.
2. How do I tell SciTE how to parse the error messages so that it
will move to the correct line (and column?) in the source file?
I've read something documenting "output.format", but don't know
how to link that with this command. Can I define a regular expression
telling SciTE how to parse the message, or is this hard-coded?
It is hard coded so you'll have to modify the source code.
Classification of the type of message is performed by
scintilla/src/LexOthers.cxx RecogniseErrorListLine and decoding into
file/line is performed by scite/src/SciTEBuffers.cxx DecodeMessage. It
is done this way to allow recognising the messages produced by
different tools within one session without the overhead of matching
many regular expressions against each line.
(Clicking on the line "Warning [flip.jss:..." does nothing; but
clicking on either of the other two messages *does* place the yellow
bullet on the correct line in the source. Why?)
The first line matches a more specific Borland format (5) rather
than a gcc error (2).
Neil
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
