-
Notifications
You must be signed in to change notification settings - Fork 44
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
WIP: Compiler Plugins #77
Conversation
Co-authored-by: Michael Chris Lopez <hello@michaelchris.space>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👁️ 👄 👁️
a36c5ad
to
0b8978d
Compare
7bd50a8
to
506092a
Compare
506092a
to
3398363
Compare
38a6ee7
to
1bd452d
Compare
BUILD.md
Outdated
- `viml`, head, convert parsed spec into viml | ||
- `lua`, head, convert parsed spec into lua | ||
- `vim_compatible`, tail, remove vim-incompatible values from highlight rules | ||
- `lush_to_viml`, head, convert parsed spec into viml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think people are moving away from viml term in favor of "vim script". neovim/neovim#16150
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have always hated "viml", feels like I am throwing up in my mouth but was never sure which to use.
👍
d1b56e4
to
a1eb8f6
Compare
a1eb8f6
to
5d53fbb
Compare
e674771
to
86dd8e7
Compare
Breaking Changes:
exclude_keys
removed in favor ofvim_compatible
plugin.Potential Breaking Changes:
lush(..., options)
asoptions = {compiler: ..., parser: ...}
, which would break the currentforce_clean
option (it would end up as{compiler: {force_clean: true}}
.lush.export_to_buffer
, superseded