Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibility of moving syntax definitions into a separate repository #170

Open
crbelaus opened this issue Jan 7, 2019 · 3 comments
Open

Comments

@crbelaus
Copy link

crbelaus commented Jan 7, 2019

There are some other language support extensions for different editors. Some of those editors directly (Visual Studio Code) or indirectly (Visual Studio Code or Atom) can use .tmLanguage syntax files.

Currently there are multiple Elixir extensions for those editors:

Each of those packages currently maintains its own, incompatible and different syntax definition.

It could be possible to split the current .tmLanguage grammars into their own repository that could then be reused by different editor support packages (including this one).

The good part is that there would be a single source of truth for the Elixir grammar definition across editors, unifying the maintenance efforts.

I could make the changes myself and submit a PR, but I prefer to discuss it first to see if it would make sense.

@crbelaus
Copy link
Author

crbelaus commented Jan 7, 2019

I thought about opening this discussion in ElixirForum instead of here since it may reach a wider audience. Finally I decided to discuss it here since the maintainers opinion is the most important one.

@josevalim
Copy link
Contributor

It is worth noting that those editors may have slightly different behaviours. For example, over the last issues there was some struggle to support both textmate and sublime text due to small differences and those are two that official support .tmlanguage.

@josevalim
Copy link
Contributor

And before I forget, thanks for the proposal @crbelaus!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants