-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Committing fails: could not read log file, Invalid argument #3800
Comments
since the last update to 2.50.00 I have this same error. Currently GitExtensions is useless for me. |
Same error here, 2.50 final |
What is the content of the |
sorry it is |
Can you disable ConEmu and see if the problem still occurs? |
Hi there, I just ran into the same issue, disabling ConEmu as @jbialobr suggested fixed the issue. NOTE: if you need additional debugging info just tell me what to try. |
Disabling ConEmu works for me too. Thank you. |
I use 2.50.01 on 2 PCs (both Win7). On one commit works fine, but on the other this issue happens consistently:
|
Also encountered this with Git Extensions 2.50.01 on multiple Windows 10 machines. Disabling ConEmu also "fixes" the issue for me. |
Can someone add instructions on how to "disable ConEmu" I have no idea what this is. |
Has the linked page been updated or changed? I look at the text in there and have no idea what to do with the info there. How do you disable ConEmu? |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
When I try to commit, I get the following error message:
(notice the missing " on the left side of the error message)
If I execute exactly the same git commit command in Git Bash, it creates the commit just fine.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
What is the expected behavior?
A successful commit.
Which versions of GitExtensions, GIT and Windows are affected by this issue? Did this work in previous versions of our tool?
GitExtensions 2.50.00 on Windows 10
The text was updated successfully, but these errors were encountered: