- changed status to resolved
Add syntax highlighting for the Opa language.
Issue #39
resolved
This plugin is directly based from the official Git repository of Opa.
Comments (9)
-
-
Please respect the code style (do as you see). There are no `.git` suffixes anywhere.
-
If you really care about .git suffixes then add an assertion to fix this once and forall for github urls.
-
By the way its positive.. I think its great that it was that easy for aszlig that he just patched everything without needing advice. Its great. Its what VAM was written for.
-
@MarcWeber I do not think adding assertions is fine:
1. it is not a real error, only code style violation. 2. it will slow down completion warmup.
I added code style rules at the top. As most of the rules can’t be checked in SCM sources loader it makes more sense to have a lint tool instead of an assertion, but I can’t enforce running it before doing a push.
-
only code style violation.
Taking your time and mine - thus adding an assertion is a way to make people get things right the first time. An alternative would be adding syntax rules - make it red :) Whatever prevents people from doing the same (little) mistake again is fine - or stop caring about it. Or tell me that I add such syntax rules for you. The keyword behavior is "being lazy" - delay action till its required and setup forces causing people to make thing right without mine/your action. I don't want to talk/think/read about cases which may never happen.
-
You mean, use custom syntax for this file and add this syntax to VAM? Good idea, will do.
-
Where is this quote from? I believe I’ve missed this message.
-
sry. first line was a quote, following lines were written by me :) I'll promise to use the preview button in the future. I just want to say: The quick bug reports show that VAM *is* used. And thats great. But I fear that too much policies and documentation will make people stop contributing because reading it takes so much time compared to the small task "adding a git repo"
- Log in to comment
