> It seems the language does not support such constructs. OK, I mentioned this because I noticed the use of `nestingLevel...()` and `CORK` stuff in the parser which are used for scopes.
> Any part of code can be placed inside the #Region ... #EndRegion, but #Region > ... #EndRegion is not a regular operator, macro or directive and does not > participate in code execution in any way: this is just a visual cue (for the > authors, not for the AutoIt), which allows to fold pieces of code. Usually > these are some logically related parts of the script - group of functions > and/or variables and so on. Yes, but these get parsed and the scope information gets reported for tags so this parser uses scopes. Even though in this case the scope has at most 2 members, I would suggest putting the parser into the group inside `tm_parser_has_full_scope()` that reports `TRUE` - the second group is more or less reserved for parsers that should return full scope but are a bit buggy which this parser isn't. This will help us keep track of which parsers report scopes and which don't - otherwise this change should have no effect on the unit tests or the symbol tree. >> Second, very minor thing is that in https://github.com/geany/geany/pull/3428 >> we changed comments for wordchars and comment_use_indent in the filetype >> config files > Fixed. Great, thanks. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/1752#issuecomment-1487520077 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/1752/[email protected]>
