You could style this delimiter in the fashion you want correct code to appear and then have the default actually be something loud and alerting so that they look correct only with the correct ending. This matches lines where a period comes directly before the EOL, and therefore matches well-formed lines. Define a delimiter with an empty open clause (looks at all lines) Close clause should be '.((EOL))' Note: This is a period, double bracket, EOL, double bracket. Set all lines to some angry warning colour by default, then override them with delimiter matching. Thought for highlighting a line missing it's closing period: Not tried, theorycrafted. Update 1 // 14 Apr - Added a whole mess of new keywords and removed duplicates. Good news, everyone! This project is being hosted on the KSP-KOS github repository! Updates to the XML made there will be mirrored here. If anybody happens to know of a way to make it highlight lines that don't have the closing period, please let me know and I'll add that in too For now, you'll just have to rely on your eyeballs to make sure you don't forget a period. end up having the blue highlight of the number disabled). I've been experimenting with way to highlight the end-of-line periods something bright so that you don't miss them, but the Define Your Language tool isn't set up to accomodate this, so it ends up screwing up other things (for instance, lines that end with a number SET X TO 1. If you're feeling uppity, you can also shoot me a PM and I'll edit it into the pastebin file for future users. If this really bugs you, you can open the 'Define Your Language' tool and manually add them in the keyword list tab. This setup is incomplete and you'll probably run into a few keywords that aren't recognized and show up as grey instead of black.

Each group of keywords has its own styler that allows you to choose a lighter color. If you prefer to use a black background, you can change the color of the recognized text in the Define Your Language tool's keyword tab. On darker background - It looks much better this way IMO.īecause the recognized keywords get turned black, this will not work on a very dark or black background. ks files should now automatically open in N++, although you may have to manually select it for ones that you already had open when you did the import. Make sure to hit 'Save As' in the Define Your Language tool. Open Notepad++ and open the 'Define Your Language' tool in the Language menuĬlick 'Import' and select the XML file that you just created. Paste the text into a notepad file and save it as 'Kerboscript.xml' = Here's a pastebin link to the XML file.=

How do i format xml in notepad++