After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 786421 - additional languages for syntax highlighting
additional languages for syntax highlighting
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: general
Flatpak Nightly Channel
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-08-17 11:44 UTC by Garrett LeSage
Modified: 2018-01-11 10:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Garrett LeSage 2017-08-17 11:44:53 UTC
Builder should have better support for additional languages, especially for web development.

I've collected a bunch of additional languages from various collections on the Internet (as not one had them all, and some were missing big gaps in web development languages).

It's only a work in progress at the moment, but it has already been useful for my own needs. I have been keeping track of them locally and have shared the git repo at:

https://gitlab.com/garrett/gtksourceview-lang-extras

(This is what's currently in my ~/.local/share/gtksourceview-3.0/language-specs directory.)

Of course, this doesn't include symbols or other nice support — just syntax highlighting — but it's a great start, as it lets me use Builder for web-based projects (instead of vim).
Comment 1 sébastien lafargue 2017-08-17 12:32:32 UTC
hi,

so what you propose is to include in Builder new .lang files that GtkSourceView doesn't want yet because they are not complete, right ?

What i see in your gitlab repo is *all* the collected .lang files, that is those from GtkSourceView and some from other sources.

So, maybe at first it will be good to separate them so we can have a better idea of new files it is about.
Comment 2 Christian Hergert 2017-08-17 19:22:39 UTC
I think it is okay for us to bundle various language specifications until better ones are provided upstream.

We can put them in a plugin and bundle them as resources, and make sure their position in the search path is low, meaning GtkSourceView .lang files take precedence.

Obviously, it would be great if this stuff was in GtkSourceView, but since I'm not an expert on those languages, I'm not in great shape to be able to state whether or not they are good enough.
Comment 3 GNOME Infrastructure Team 2018-01-11 10:38:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-builder/issues/269.