Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm writing in a user-defined language called 'Umajin' (*.u), which has a syntax quite different from C/C++ or any ECMAScript-based language, so we've had to write in the rules for the highlighting.

I've been trying to write parser rules for the language for function-list to pick up, too - but find that every time I try to add a rule through the dialog, it causes NP++ to crash. This goes for the portable version as well as an install reading from %APPDATA%. If I go into the FunctionListRules.xml and drop rules in for Umajin there, I can see them when I open the 'Language Parsing Rules' dialog, but they don't have any effect when viewing a .u file.

I have found, however, that if I clobber the settings for another existing language (I'm overwriting python, since it's closest in syntax), and then manually set the language to Python for any given file, the rules parse correctly and give me what I want. The only problem being that I can have highlighting, or function listing, but not both!

Has anyone managed to drop parsing rules into Function List for an entirely new language?

For reference, I'm using Notepad++ 5.8 unicode and Function List 2.1 unicode, running on Win7 Enterprise and Ultimate.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.