-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Headless Install of VIM Plugins #123
Comments
Hey @enggnr --- I just checked the |
We need to figure out the proper command to add to the |
This works on a new installation. The plugins were all installed OK. Please see the related comment on #126. |
Does this work on macOS?
…On Sat, Dec 23, 2023, 9:00 AM enggnr ***@***.***> wrote:
We need to figure out the proper command to add to the astronvim section
in the software.yml file that currently reads: _post: bash -ci "nvim
--headless -c 'quitall'"
This works on a new installation. The plugins were all installed OK.
Please see the related comment on #126
<#126>.
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOJRHXO4VA4TMTWCVLSE6TTYK3PXBAVCNFSM6AAAAAA73USXWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGMYDAMJWGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yes. Tested on MacOS and Ubuntu. |
❔ What are you experiencing an issue with?
Latest Release
❔ Version
N/A
🐞 Description
Currently, on macOS - the automatic installation of VIM plugins is not fully being done ahead of time. The recommended
vim +PlugInstall +qall > /dev/null
seems to work for the regular plugins but the coc plugins are not automatically installed. When you open VIM, they open a second pane and start installing even after the PlugInstall command is run. The coc plugins should be installed ahead of time as well.Please make sure the plugins are also automatically installed with nvim as well as regular vim.
⏺️ Steps To Reproduce
No response
📒 Relevant Log Output
No response
💡 Possible Solution
No response
The text was updated successfully, but these errors were encountered: