-
Notifications
You must be signed in to change notification settings - Fork 0
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
No syntax highlight on jinja files #102
Comments
Maybe you need at least to replace : "start": "{%\\s*(block|filter|for|if|macro|raw)",
"end": "{%\\s*end(block|filter|for|if|macro|raw)\\s*%}" by : "start": "\\{%\\s*(block|filter|for|if|macro|raw)\\}",
"end": "\\{%\\s*end(block|filter|for|if|macro|raw)\\s*%\\}" |
The underlying issue is probably this: eclipse-tm4e/tm4e#677 |
Thanks, I'll try that ASAP ! This comment is not relevant even if it's not the cause of the problem ? EDIT : still not working for me. And the same message appears in the logs |
I already fixed this in TM4E. The snapshot version is able to parse this. |
Better with TM4E 0.9.0 : jinja expression are well highlighted but not the json part. Don't know if it is working as intended. I still have the "Failed to parse pattern" logs though. EDIT : ok I'll try the snapshot of TM4E :) |
No more error logs with the latest snaphot but still no syntax highlight for the json syntax in the file. Curiously, if I paste my code in the "preview" section of the "Text Mate" > "Grammar" > "test.json.jinja" configuration page, it is working as expected |
I figured out the root cause, looks like eclipse does not like mapping content types to file extensions that contain a dot, e.g. |
Tested this morning with the latest version and it's working as expected now ! Thank you very much for your support :) |
Hi,
I've installed the plugin on Eclipse2023-12.
Version: 2023-12 (4.30.0)
Build id: 20231201-2043
I have no syntax highlight on a text.json.j2 file.
In the error log I have this :
Here is my installation details :
The text was updated successfully, but these errors were encountered: