Edit in vscode opens extra files corresponding to vscode switches

[lonix1]

I'm using vscode with the c# extension, on linux.

I added this config to open files in vscode when pressing e:

os:
  editPreset: 'vscode'
  editAtLine: 'code --goto {{filename}}:{{line}}'

That works... mostly.

From time-to-time it correctly opens the file at the appropriate line, but also opens two new (unsaved) empty files at the repo's root: --log and ms-dotnettools.csharp=info. Those files seem to be switches passed to vscode which are somehow interpreted as files (and thus opened).

I don't open vscode that way - I always use the normal code .

Why/how is lazygit determining those switches, and how do I stop it from passing them to vscode?

[stefanhaller]

I have absolutely no idea what's happening here. Lazygit is certainly not the one that adds those switches, but I have no explanation for who else might be doing that.

If you look at the Command log panel in the lower right of lazygit's window, it should show the command that lazygit uses to edit the file.

Unrelated question: is it on purpose that you explicitly define editAtLine? It is not needed, selecting an editPreset should be enough. It defines editAtLine too, but the vscode preset also includes --reuse-window.

[lonix1]

Thanks, I didn't know about the command log. It shows /usr/bin/zsh -c "code --reuse-window --goto --"/home/username/work/Foo.cs":964" - so as you suspected Lazygit does not send any extra switches.

I think I added editAtLine because I saw the default in the docs was empty. I suppose that's because it differs based on IDE. I removed it as per your recommendation and it works properly.

Thanks for your help. Must be a weird VSCode or VSCode-C# extension issue.

[lonix1]

BTW if anyone else runs into this issue, I opened an issue on the vscode-csharp repo.