Closed avalonwilliams closed 4 years ago
The git status command currently locks out the git index file, which prevents users from using git commands while it is running.
As a result, while our async prompt is loading, it prevents users from running a git command.
This isn't a big deal for small to medium sized projects on modern computers, however it poses a large problem on very large codebases.
A possible way to fix this is using git's --no-optional-locks flag.
--no-optional-locks
The --no-optional-locks flag first appears in git 2.14.0, which is relatively recent, so checking the git version is probably needed.
The git status command currently locks out the git index file, which prevents users from using git commands while it is running.
As a result, while our async prompt is loading, it prevents users from running a git command.
This isn't a big deal for small to medium sized projects on modern computers, however it poses a large problem on very large codebases.
A possible way to fix this is using git's
--no-optional-locks
flag.