Hi David,
I hope this helps a bit...
background:
Slick displays an internal buffer '.process' in the 'Build' window used to capture the output of the shell / tools running there.
We only have to setup a file extension 'process', a lexer for the contents there and assign it to the 'process' file extension.
Slick uses that setup even though '.process' is not a real file.
1.) start from scratch:
- 'Tools->Options->File Extension Setup -> Advanced Tab
- 'Click 'New' (bottom of the dialog)
- enter <process> referring to '(none)'
- click on 'Color Coding' (lexer field is empty)
- Slick tells you that there is no lexer defined for 'process' and asks you to define one.
- start defining your lexer ...
2.) start w/ defining a lexer and assign it later on when you defined the new 'process' file extension:
- 'Tools->Options->Color Coding
- 'Click 'New'
- define your process buffer lexer
- 'Tools->Options->File Extension Setup -> Advanced Tab
- 'Click 'New' (bottom of the dialog)
- enter <process> referring to '(none)'
- choose your prev. defined lexer
Good luck,
HS2