pug-tmbundle
pug-tmbundle copied to clipboard
davidrios
Looking for new maintainer
Hi all,
It has been quite a while now since I last used Jade/Pug, and I don't see the reason to use it anymore going forward. I kept updating the bundle anyway, but now, with the new versions of Sublime Text and the problems this bundle is causing, also the fact that Pug continues to evolve, the ideal thing would be to rewrite it using the newer format and add the missing new functionality. The problem is that that's really not on my priorities list so, if anyone is willing to help in keeping this project alive, let me know so I can add you as a contributor. If you decide to fork it instead, I'm OK with that too.
Cheers
Hi! I am using Pug a lot in my projects and want to improve the syntax or at least fix bug with filters.
But I am completely disoriented in all these formats. Where do I start?
Hi,
Nice. The file you need to edit is Syntaxes/Pug.JSON-tmLanguage. It's generally documented with comment attributes explaining what each definition is for. After the edit is done you need to compile it to a plist xml, and for that you need https://github.com/SublimeText/PackageDev installed. This definition is still using the legacy format, so keep that in mind when looking for information on the internet.
Take a look at the official documentation for in depth information: http://docs.sublimetext.info/en/latest/extensibility/syntaxdefs.html The examples on that page are using the YAML format, you just have to adapt to JSON for this package.
Hi @davidrios, I'm open to taking this on or at least providing some interim maintainership.
One of the first things I'd want to do is add CI and do some automated testing against pug files.
I wrote a very rudimentary test for one of my own repos for a Splunk .conf file sublime package (see test.py: https://github.com/shakeelmohamed/sublime-splunk-conf-highlighting
If we write up test cases for everything that's broken, then it'll be really easy to verify fixes where highlighting breaks.
