Hello there,
I am setting up your dotfiles on [Your OS, e.g., Fedora 42], and I encountered a persistent issue while installing plugins via Lazy.nvim.
The copilot.lua plugin fails to install because it attempts to use the SSH protocol for cloning, which fails if the user hasn't set up an SSH key.
Steps to Reproduce:
- Cloned the dotfiles repository.
- Created the symlink for the
nvim configuration to ~/.config/nvim.
- Launched
nvim, which automatically initiated plugin installation via Lazy.nvim.
Expected Behavior:
The copilot.lua plugin should install successfully.
Actual Behavior (The Error):
The installation fails with a clone failed error, indicating an issue with the SSH connection attempt:
Failed (1)
o copilot.lua @ BufReadPost @ Copilot = clone failed
...
remote: Compressing objects: 100% (313/313), done.
...
warning: clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD .'
Proposed Solution (Optional):
To ensure installation works out-of-the-box for users who rely on HTTPS, perhaps changing the plugin source definition in the configuration files to explicitly use the HTTPS URL for cloning would resolve this dependency issue.
Thank you for your work on these dotfiles!
Hello there,
I am setting up your dotfiles on [Your OS, e.g., Fedora 42], and I encountered a persistent issue while installing plugins via
Lazy.nvim.The
copilot.luaplugin fails to install because it attempts to use the SSH protocol for cloning, which fails if the user hasn't set up an SSH key.Steps to Reproduce:
nvimconfiguration to~/.config/nvim.nvim, which automatically initiated plugin installation via Lazy.nvim.Expected Behavior:
The
copilot.luaplugin should install successfully.Actual Behavior (The Error):
The installation fails with a
clone failederror, indicating an issue with the SSH connection attempt:Proposed Solution (Optional):
To ensure installation works out-of-the-box for users who rely on HTTPS, perhaps changing the plugin source definition in the configuration files to explicitly use the HTTPS URL for cloning would resolve this dependency issue.
Thank you for your work on these dotfiles!