Skip to content
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

Contribute runtime files to vim #565

Open
flwyd opened this issue Oct 22, 2022 · 2 comments
Open

Contribute runtime files to vim #565

flwyd opened this issue Oct 22, 2022 · 2 comments

Comments

@flwyd
Copy link

flwyd commented Oct 22, 2022

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.

@jbodah
Copy link
Collaborator

jbodah commented Oct 22, 2022

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.

@ghost
Copy link

ghost commented Oct 13, 2023

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. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants