-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
schemedef does not handle dashed for comments #6
Comments
Please attach the schemedef you're trying to use, I'll see if I can work out what's happening when I get some time. |
Hi Simon, attached you find the schemedef file. Thanks
|
Hmm, sadly attachments don't work for the github tracker. Please either put it in the text, or (better) follow the instructions here to create a gist and send me the link: ned14/BEurtle#1 |
Here's the download link for the relevant schemedef and a source sample Cheers
|
Ok, I think in this case it's because numbers have a higher priority than comments (which is perhaps a mistake). -- matches both your comment configuration, and also your number configuration (starts with -, contains -). I think if you remove the ability to start a number with -, then it should work? e.g.
Let me know! |
Hi Simon, I've already tried that countless times. Cheers Simon Steele schrieb:
|
Ah, apologies, so it's not just numbers that take preference but also keywords. If unspecified keywords have a start set that includes '-' as well. So the combination of these two works for me: <keywords start="[a-zA-Z0-9_]" />
<numbers start="[0-9]" content="[0-9.]" /> |
Aaaaah... now that did it! One more question though: Exit south To bar Can I somehow make PN recognize the integrity of such control structures. Begin_keywords: If then in Cheers Simon Steele schrieb: |
There's no way to do this with a custom schemedef, you'd need to write a Scintilla lexer in C++ and it would be non-trivial - most lexers avoid needing to keep much state between lines. |
Trying desperately to create a schemedef for AlanIF - an adventure language like Inform6.
For this I have to declare a double dash -- as the beginning of a line comment.
This seems to be completely ignored by PN. PN tries to parse the comment lines without recognizing them as comments.
Please help. This bug is driving me nuts.
The text was updated successfully, but these errors were encountered: