Add ocamllex highlights #549
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
undu
force-pushed
the
ocamllex
branch
2 times, most recently
from
7d3e775 to
04da351
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The parser emits opaque
ocamlnodes, since these are not yet handled to the ocaml parser they remain unhighlighted. The ocaml nodes appear inside action nodes. I've tagged those with@embeddedsince that's how it seems to be handled in other scm files. is this how it's supposed to be used?I've added the hash to the lockfile, although it's not clear in the diff since it's all in the same line.
Like it happens to highlight mli files, this PR is needed: ocaml/vim-ocaml#61 (or set manually the filetype to ocamllex)