Debug lines highlighting works fine, thank you! I've just send the three lists to you via PM.
The other open COBOL points: 1. All entries appear in the code explorer, even if they are commented out. Could you filter the divisions/sections that are only comments? 2. I doesn't know of any of the PreprocessorWords from your list. Where are they from? 3. A lot of COBOL words have their ending pairs (if end-if; evaluate end-evaluate; display end-display; ...) it seems only if end end-if are marked as belonging together. Can you change this, too? 4. What should the Context/COBOL.DEF do? It seems to be broken to me. 5. These two files types are often used as a COBOL copy (same like a #include in C++), maybe you want to add them to the "standard file extensions" for Cobol scheme: copy cpy (I've done this manually). 6. The last point - Preprocessors: There are a lot of preprocessors for different things in COBOL available. One of the most things are SQL-Preprocessors, but the syntax between them differ a lot. There are other preprocessors for company specific things. These could not and should not be implemented into the standard COBOL syntax scheme but it would be useful if one could manually add them. I think of something like a multi level syntax scheme: Use the COBOL one shipped with PSPad, define another one for the preprocessor(s) in use and enable them both at one time. Is this possible with recent PSPad in some way or could this be implemented? human -- <http://forum.pspad.com/read.php?6,49176,49259> PSPad freeware editor http://www.pspad.com
