zawys

I'll consider it. For now, you can follow [the manual installation steps](https://github.com/zawys/vscode-as-git-mergetool#installation).

> Given #10 and #11, is there something dumb I'm doing? No, I can reproduce this too. I didn't work on this repository for a while. It's amazing how fast...

Maybe the quickest way to fix the issues would be to setup the repository again based on the current recommendations.

Hello! Thanks for your interest in this project. I also wanted to have such feature. Approaches coming to my mind: 1. Change VS Code's CLI such that you can pass...

What happens when you open a terminal, `cd` to the root of the affected repository, and manually run the command `git mergetool`?

I agree. Those warnings look weird but probably have nothing to do with `git mergetool` and are probably a pipe reuse issue with VS Code / NodeJS. Would it be...

When you run `git mergetool` from terminal, is the merge conflict opened in VS Code?

Hi @mvoppen! 1. As stated in a [previous comment](https://github.com/zawys/vscode-as-git-mergetool/issues/2#issuecomment-702075203), sometimes error messages from unrelated child processes of VS Code are printed into the terminal. I think this is an issue...

Thanks for your detailed answers! That was fun! Let’s repeat it for a while! ;) Sorry if I’m wrong about how WSL works – I currently don’t have access to...

Thanks again! Very insightful. 1. That `code` is not in $PATH in your WSL environment seems to be different from the setup described in the [VS Code documentation regarding WSL](https://code.visualstudio.com/docs/remote/wsl#_opening-a-terminal-in-wsl)....