I know of no way for a package that’s been added to the ignored_packages
setting to still be somehow loaded after a restart.
I believe that the package name is derived from the name of the directory that the package is installed in, so if it was stored in some package other than GitGutter
, I suppose that would do it. Something like that could happen if you manually installed the package in a directory other than GitGutter
or if the directory somehow got renamed (maybe during the package upgrade process? I don’t know).
The default one or the one in your User
directory? The default one shouldn’t be empty. If it is, that may be the issue and reinstalling the package might help (assuming you can determine why it still works even when it’s disabled, anyway).
If you don’t explicitly set the git_binary
setting to point at the git executable directly, it defaults to searching through your system path to try and find it. The error message appears in the case that there’s no setting telling it where the binary can be found AND it’s also not available in the system path.
For the sake of reference, on my Linux and MacOS machines this is /usr/bin/git
, while on my Windows machine it’s installed at C:\Program Files\Git\cmd\git.exe
; your mileage may vary though, since I can’t recall if the windows version asked me where it should install or if it picked that location on it’s own.
Since the default path under Linux and MacOS generally always contains /usr/bin
the only machine I had to configure was my windows machine, where I chose to add the proper location to the system path so I didn’t need to have a system specific setting just for Windows.