Re: Segfault in git when using git logs
- From
Sathyajith Bhat <sathya@sathyasays.com>
- Date
- Nov 3, 2020, 18:55 UTC
- Message-ID
- <CAMsWJsxyW=JUh=XGCkGG3LhOsZASwFHtx9b6ziNi_uHa918Scw@mail.gmail.com>
- In-Reply-To
- <0581272e-6ad2-42d9-0196-b804ee304619@gmail.com>
On Tue, 3 Nov 2020 at 20:46, Derrick Stolee <stolee@gmail.com> wrote:
Show 8 quoted lines
> Hi Sathyajith, > I started filling out an issue on the VS Code GitHub repo > so they could perhaps fix their usage of "git log" in this case. > However, I started searching their code for where they might > be executing the command, and I didn't find anything! > > Is it possible that you have an extension that enables Git > history commands like this?
Hi Derek,
I believe it is GitLens [1] which is causing the incorrect behaviour. I haven't had any crashes after I disabled GitLens, and that's the only extension I've had which interacts with scm.
[1] https://github.com/eamodio/vscode-gitlens
thanks, Sathya