highlightjs / highlightjs-extempore Goto Github PK

lexemes doesn't do anything unless paired with keywords which you aren't using (that I can see). So you could remove it entirely.

Users finding your repo from the SUPPORTED_LANGUAGES list will expect to find up-to-date instructions on how to add your 3rd party grammar to their project. Your current instructions are very old and incorrect/outdated. There are now clear standards for how 3rd party grammar repos should be structured. Please see the examples below.

• On the client-side ship a dist build (which our build script can help you generate). See https://github.com/highlightjs/highlight.js/blob/master/extra/3RD_PARTY_QUICK_START.md
• On the server-side ship a npm module (that someone can use to extend our library).

Please see:

• https://github.com/highlightjs/highlightjs-robots-txt (a example README)
• highlightjs/highlight.js#3008

#3008 is specifically related to upgrading from v10 to v11 but it still applies to the proper way to structure your repo to make it easiest to use for the most people.

Can we change the top-level naming stuff for this language to be extempore rather than xtlang?

The reason is that Extempore includes both Scheme and xtlang, and so calling the whole thing xtlang (e.g. in hljs.registerLanguage('xtlang', ...) is too confusing.

I guess this means that we'll change the filename to extempore.js. I realise that the repo itself is called highlightjs-xtlang, but I don't think we need to change that for now - the intention is clear.

If you're using one of the standard OSS licenses could you please add that so it's clear? Or are you truly using a custom license?

As a maintainer of a Highlight.js language grammar you might be interested in the discussion of an official packaging format. I just created an issue to track the discussion and I've been working on this along with the new build system.

highlightjs/highlight.js#2328

Sorry for the spam, but I couldn't think of an easier way to ping the people who might be most interested in weighing in on the subject. Feel free to simply close this issue or leave it open (whatever works best for you!).

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.