We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
git.default_url_format
nvim --version
NVIM v0.8.1 Build type: Release LuaJIT 2.1.0-beta3 Compiled by runner@fv-az178-366
git --version
git version 2.34.1
-OS: Ubuntu 22.04 WSL2
I set the default_url_format to https://hub.fastgit.xyz/%s before, but this site has been closed. This is my new config:
default_url_format
https://hub.fastgit.xyz/%s
return require('packer').startup({ function(use) -- packer itself use 'wbthomason/packer.nvim' -- ignore some config end, config = { max_jobs = 16, git = { default_url_format = 'https://github.com/%s', }, display = { open_fn = require('packer.util').float, } }, })
I execute the PackerCompile after modify. And the actual url of plugins in plugin/packer_compiled.lua is changed to https://github.com/%s correctly.
PackerCompile
plugin/packer_compiled.lua
https://github.com/%s
When I run PackerUpdate, packer will visit the github.com to clone these repositories of plugins.
PackerUpdate
github.com
It still redirect me to hub.fastgit.xyz/%s.
hub.fastgit.xyz/%s
The text was updated successfully, but these errors were encountered:
No branches or pull requests
nvim --version
git --version
-OS: Ubuntu 22.04 WSL2
I set the
default_url_format
tohttps://hub.fastgit.xyz/%s
before, but this site has been closed. This is my new config:I execute the
PackerCompile
after modify. And the actual url of plugins inplugin/packer_compiled.lua
is changed tohttps://github.com/%s
correctly.Expected behaviour
When I run
PackerUpdate
, packer will visit thegithub.com
to clone these repositories of plugins.Actual behaviour
It still redirect me to
hub.fastgit.xyz/%s
.The text was updated successfully, but these errors were encountered: