You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In software.yml, the AstronVim entry includes nvim --headless 'quitall' but when it is run it generates a bunch of errors including:
Error detected while processing /Users/bzalewski/.local/share/nvim/lazy/lazy.nvim'...
fatal: unable to access 'https://github.com/folke/lazy.nvim.git/': Could not resolve host: github.com
Both vim and nvim need some love to make sure they are configured properly and make sure their plugins pre-install. There might be a few issues related to this that are open. Please treat this as the priority since we have had this issue for awhile.
⏺️ Steps To Reproduce
No response
📒 Relevant Log Output
No response
💡 Possible Solution
No response
The text was updated successfully, but these errors were encountered:
@ProfessorManhattan, I am unable to reproduce this problem when setting up Astronvim. It works for me on Ubuntu and a Mac. However, I saw this at times Could not resolve host: github.com during the setup. Most of what I read points to exhausting GitHub API limits and some due to network errors. I also found that the value of http.sslcainfo could be a reason (fixed it for Linux installations). If this was pointing to an invalid file, git clone fails (which brew uses as well). Could you please check if any of the above is the case? Neovim works OK after this.
❔ What are you experiencing an issue with?
Latest Release
❔ Version
N/A
🐞 Description
In
software.yml
, the AstronVim entry includesnvim --headless 'quitall'
but when it is run it generates a bunch of errors including:Both
vim
andnvim
need some love to make sure they are configured properly and make sure their plugins pre-install. There might be a few issues related to this that are open. Please treat this as the priority since we have had this issue for awhile.⏺️ Steps To Reproduce
No response
📒 Relevant Log Output
No response
💡 Possible Solution
No response
The text was updated successfully, but these errors were encountered: