Timeline for Highlight syntax in start and end delimiters of region
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2019 at 5:21 | history | edited | filbranden | CC BY-SA 4.0 | added 726 characters in body |
| Dec 19, 2019 at 5:17 | vote | accept | Caleb | ||
| Dec 19, 2019 at 5:11 | comment | added | Caleb | I just tried and it is indeed much more stable. Thanks for the trick. | |
| Dec 19, 2019 at 5:06 | comment | added | filbranden | Ah you're the author of the plug-in! 😁 I didn't realize that... Yeah that's totally fine, thanks a lot for the attribution! Really happy to have helped here. | |
| Dec 19, 2019 at 5:04 | comment | added | filbranden | Glad this worked for you! You can try changing the end tag to end="\\end{script}"me=s-1 (change match eend to one character before the start of the regex), in which case the \\end{script} will be outside the region and might be a lot more stable... (Let me know if that helps, I can update the answer to include that too!) | |
| Dec 19, 2019 at 5:03 | comment | added | Caleb | I hope you don't mind I credited you as the author of the code in the commit where I added this. If you don't wish for that I'm happy to overwrite it without the credit. | |
| Dec 19, 2019 at 4:49 | comment | added | Caleb | Wow, thank you, and that works beautifully. It's rather amusing how the \end{script} delimiter changes highlighting when entering incomplete Lua code (such as when it's looking for an end to finish and un-closed loop, but I think that's to be expected. At least it doesn't bleed all over the rest of the file like my previous attempts. | |
| Dec 18, 2019 at 17:11 | history | answered | filbranden | CC BY-SA 4.0 |