* Skip removed grammar submodule
* Clean up old grammar from grammars and grammars.yml
* Clean up unused grammar license
Run `script/licensed`.
This was missing change in 12f9295 of #3350.
* Clean up license files when we replace grammar
Update license files by running `script/licensed`.
Since we replace grammar, the old grammar license must be removed
and new grammar license must be added.
* Remove trailing spaces
* Setup Bundler in some scripts
* Update grammar index
* Make prune-grammars script to be callable in a script directory
* Prune unused xquery grammar repo
source.xq by language-jsoniq is actual tm_scope for XQuery.
* Remove xquery submodule
git submodule deinit vendor/grammars/xquery/
git rm vendor/grammars/xquery/
* Fix invocation of script/list-grammars
This fixes#3339.
* Make add-grammars script to be callable in a script directory
* Generate samples.json before running list-grammars
list-grammars requires linguist.
Sublime Text YAML syntax definitions use the .sublime-syntax file extension
Most syntax files declare a YAML 1.2 syntax although they are YAML 1.1 compatible
Thus, the YAML version header is stripped off before parsing
Displays a warning if parsing fails
In .sublime-syntax files, the scope is under the 'scope' key -- as opposed to the usual 'scopeName' key
* The `thread`-gem is required for the script, because otherwise Ruby throws an error that `Queue` in line 259 is an uninitialized constant
* The variable `p` was previously in the same method with the status message saying `OK ‹path› ‹converted scopes›`. But `p` is now defined in load_grammars() and thus not visible when showing the OK-message in install_grammars(). This was solved by adding a path-parameter to install_grammars().
convert-grammars now supports a few flags that we can use to make it
dump out the YAML just for the local grammar submodules. We can then
compare this to the YAML that's actually in grammars.yml to check that
they're the same. If they aren't, grammars.yml needs to be updated.
This will help catch mistakes like using the wrong scope name.
