On 18/05/2012 16:21, Homme, James wrote:
> I was trying to set up abbreviations that would help me write t2t files. As I was looking
> through the various properties files and trying to trace what would happen when I worked
> on a t2t file, I saw that the global properties file has a lot of import lines in it for
> various languages, and none of them end with ".properties." I'm assuming from this that
> SciTe somehow knows that it should add this extension. Is this right?
Note: software's name is SciTE (TE = Text Editor, Sci = Scintilla, the component
displaying the source code).
> Next Question. When I save or open a file and give it a t2t extension, is that when SciTe
> understands that it should use my t2t.properties file?
You include t2t (in SciTEUser.properties), and this file should define the extensions
associated to the t2t lexer (or another, close of the syntax you need).
> Next question. Should I create an import line in my t2t.properties file for
Yes, it is not automatic. Most language property files doesn't have an abbreviation file,
these are generally more user-specific. Some languages property files have an API file,
For example, I have a api.$(file.patterns.lua)=$(SciteDefaultHome)/lua5.api
But again, these should go to SciTEUser.properties, unless you always require the API or
abbreviation file to be shipped with your t2t.properties.
> Next question. Does all of this mean that my t2t.properties file only acts on t2t files,
> if t2t.properties is in use?
An import is always imported, regardless of the current file / buffer. Beware of conflicts
with other properties files!
So, your t2t.properties should define only properties for this kind of file.
if you defined this property (useful if you have several extensions attached to this lexer).
-- (near) Paris -- France
-- -- -- -- -- -- -- -- -- -- -- -- -- --