-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
Hang at startup when $GIT_DIR is set #500
Comments
For more info about the plugins I use see: wbthomason/packer.nvim#465 |
could not reproduce the lag, can you give me a minimal sample config from which you can reproduce the error (like only a packer and nvim-tree with config options or not ?) |
I can reproduce it with: require('plugins')
local execute = vim.api.nvim_command
local fn = vim.fn
local install_path = fn.stdpath('data')..'/site/pack/packer/start/packer.nvim'
if fn.empty(fn.glob(install_path)) > 0 then
fn.system({'git', 'clone', 'https://github.com/wbthomason/packer.nvim', install_path})
execute 'packadd packer.nvim'
end
local packer = require('packer')
return packer.startup(function(use)
-- Plugin Manager
use {'wbthomason/packer.nvim'}
-- File explorer
use {'kyazdani42/nvim-tree.lua'}
end) Make sure to clear your compiled To trigger the hang: cd
git clone https://github.com/kyazdani42/nvim-tree.lua
GIT_DIR=nvim-tree.lua/.git nvim
If I don't set GIT_DIR all is good. |
very weird indeed, i think this might be caused by too many git changes and a lot of git commands issued actually. It's not really something that i can fix imo. |
i managed to reproduce only running nvim from a big directory (Home in my case) |
Ok thanks for looking into it ! |
I have exactly this issue. |
i'm currently rewriting the git module by running git commands in jobs to avoid blocking nvim. It will probably help a lot. |
I'm closing this in favor of #549 :) |
When setting
GIT_DIR
to a .git folder, nvim hangs for ~10s at startup.To reproduce:
It doesn't occur when I remove
nvim-tree
.The text was updated successfully, but these errors were encountered: