-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble resolving merge conflicts with Mercurial and vscode #32
Comments
Using hg 4.2.1 |
Same thing with mercurial 4.3.1, VSCode 1.19.2 on Linux |
I have exactly the same problem on Linux Mint 17.2. HG: 4.4.1 This makes it impossible for me to use VSC :( |
@P9GIT As a workaround, you can right-click on the file and select "open files". Could it be possible to make it the default behavior? |
Hi @ghusse Thanks for your suggestion. |
any progress on this? how can I help? maybe provide some logs? |
I can confirm this issue is still reproducible: Error: |
Released in v1.5.1. Thanks @incidentist! |
I have done a simple
hg merge branch
into my current branch.2 files are in merge conflicts. They are shown correctly separate from the other files that were auto-merged.
However when trying to open the conflict files to see the comparison about what changed I get the following error:
Unable to open 'gulpfile.js (local <-> other)': Unexpected token p in JSON at position 0.
Also when trying to resolve the file, I get this error:
'echomsg' is not recognized as an internal or external command, operable program or batch file.
in the hg output log.
Don't really know what other information I could provide?
The text was updated successfully, but these errors were encountered: