Contribute runtime files to vim
flwyd opened this issue · comments
The feature wishlist in the README includes "Regularly merging vim-elixir into vim and keeping the sync up-to-date" but I don't see an issue tracking it.
In the absence of a regular process for doing this, would it be possible to do it once? https://github.com/vim/vim currently has filetype detection and basic ftplugin config for elixir and heex (but not `eelixir). It doesn't have any syntax or indent files for the language, so editing Elixir files with a standard vim install is a pretty spartan experience.
I agree that this is something we should do. I am trying to be 100% hands off on this project at the moment and have reached out to several potential people who may be interested in helping takeover maintenance this project. This feels like a good first task.
In the case of Vim, the discussion to add HEEx support happened on a pull request: vim/vim#11169 (it is forwarded automatically to the vim-dev maillist, so it reduces the entry barrier).
I see some similarities between vim-ruby and vim-elixir.
The syntax file included with $VIMRUNTIME for eruby is identical to the one provided by vim-ruby/eruby (except for a comment mentioning who is the release coordinator).
Same story with the rest of the files (ftplugin, ident, compiler, ...).
Updates happen from time to time to sync the $VIMRUNTIME with the vim-ruby repository: vim/vim@da16a1b.
Sometimes, the neovim community cherry-pick patches from vim to integrate them into their runtime: neovim/neovim@61ccdb2.
With all this context, I think the process would envolve designating a release-coordinator and submitting the necessary files.
Hope this comment shed some light on this issue. 🙂