-
Notifications
You must be signed in to change notification settings - Fork 16
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
Code highlighting for V1 #397
Comments
I don't think it's worth supporting it, it's a very niche project, it has just 3 stars in Github and doesn't seem to have any real user besides its developer. There are currently thousands of hobby programming language projects, I need to be mindful in supporting new languages, I think unless there's an actual user of ecode needing the language support I won't add them myself... unless I can convert the syntax rules from other editor very quickly as I did from Fennel from example, since it's supported by lite-xl and ecode has a tool to convert those language definitions directly from lite. I'll do the same with Blade, since that takes me less than 5 minutes. Documentation for adding custom languages support is here. And of course you're more than invite to collaborate :) |
Thats right, but V1 is developed since 2016 and well documented. It has a C/C++ API to integrate it in own applications. |
@mwiedeV1 Just to clarify, I didn't want to sound disrespectful, it was just an observation, anyone is more than invited to add v1 syntax highlighting to ecode, it's just I did not expect that to happen due to the lack of popularity, of course if any of you two is willing to do it you're more than welcome, I'll reopen the issue to be clear that I'm open to the possibility. |
I just help him. |
I have a quick and dirty hack for V1 syntax highlighting on ecode: treat V1 source code as PHP. I think it will work. |
V1 is a simple interpreted language. I think I could modify the code highlighting rules for PHP to add support for it, but I don't know how to and where to start.
The text was updated successfully, but these errors were encountered: