-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Split Vim extensions into separate repository #3756
Comments
I've created a separate repository for the Vim extensions(with full history): https://github.com/berkerpeksag/vim-rust/commits/master You can fork/transfer this repository into Mozilla organization or just import $ git init
$ git am < vim.patch
$ git push -u <your_remote_name> master I can open a new pull request to remove the |
Please split vim extension into a seperate repo. It is not difficult, but helpful. |
@upsuper you can use the vim-rust repo until this issue fixed: https://github.com/berkerpeksag/vim-rust |
Not critical for 0.6; removing milestone |
Nominating for milestone 5, production-ready |
Is this true for emacs too? |
not accepting for milestone. (may or may not actually take action on this bug eventually, but did not close outright during triage.) |
Triage: no change, the canonical source is still |
Ping? This would be great to separate out to a different repository as it would make installing rust vim plugin with pathogen a breeze. |
@huonw nice, thanks for the link. Are there any plans to separate the code out? I can imagine it would make maintaining it, using it and contributing to it a lot easier. |
ok, wish this can be done. |
Reasons for this? |
The extension is now in a separate repo, thanks to @steveklabnik: https://github.com/rust-lang/rust.vim |
Add `gettid` support Add support for `gettid` in miri. To ensure that the requirement that `getpid() == gettdi()` for the main thread, we use the value returned by `getpid` and add to it the internal thread index. Since `getpid` is only supported when isolation is disabled, and we want `gettid` to be used both in isolated and non-isolated executions, we modify `getpid` to return a hardcoded value (1000) when running in isolation mode. Fixes rust-lang#3730
Currently the Vim extensions are in a subdirectory in the main repository, specifically here: src/etc/vim.
This makes it less user-friendly with Vim extension handling tools like VAM, Vundle and Pathogen that rely on separate git repositories for handling each separate extension.
While it is possible in Vundle to configure a "run-time path" such that a subrepository is chosen, this might be less optimal.
This is because the whole rust repository (which is fairly large) must be checked each time when installing/updating vim extensions, instead of only the smaller vim-related parts.
On my computer this takes at least one minute, which is a reasonably long time considering the parts needed.
The text was updated successfully, but these errors were encountered: