wslgit: Issue with bash not showing the commit details in Fork
Just recently, I noticed that Fork was not showing the ‘Commit/Changes/File Tree’ pane, with an error message:
/bin/bash: !--RevisionMessageEnd--; No such file or directory
At first, I thought that the issue is with Fork, so I tried reinstall Fork, but the issue still persist.
The message disappeared only when I changed the Git Instance under preference to the default git that was include with the app.
So it’s suggesting to me that the issue is with the wslgit symlink.
I’m using Fork Version 1.80
Hope you can help me,
Thanks
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 7
- Comments: 18 (5 by maintainers)
Commits related to this issue
- Escape `<`, `>` and `!` characters in arguments Fixes Issue with bash not showing the commit details in Fork #134 — committed to carlolars/wslgit by carlolars 2 years ago
- Escape `<`, `>` and `!` characters in arguments Fixes Issue with bash not showing the commit details in Fork #134 — committed to andy-5/wslgit by carlolars 2 years ago
There is now a test build of
wslgitwith the fix by @carlolars available for download.The problem is that Fork changed one argument to
--pretty=format:%H±.%aN±.%aE±.%at±.%cN±.%cE±.%ct±.%P±.%B<!--RevisionMessageEnd-->, and bash don’t like unescaped<,!and>. I have implemented a fix that I’m testing now.@MichalGow Yes, the
--diff-merges=1flag seems to be a quite recent addition to git. I think you need at least version 2.31. There is nothing wslgit can do about that.@DanPristupov I think there is no need to change the separator, now that wslgit can properly escape the special characters.
New wslgit (1.2.0-alpha3) doesn’t work for me. Now I am getting fatal: unrecognized argument: --diff-merges=1
Which needs to be fixed by updating GIT inside WSL - https://unix.stackexchange.com/questions/33617/how-can-i-update-to-a-newer-version-of-git-using-apt-get