-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Output from git commands not visible in GitBash #2064
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
Comments
Is this still happening with v2.21.0-rc2? |
Still happening with v2.21.0 Note that preceding commands with winpty will cause the output to be displayed. As a workaround this is OK but it appears that the main purpose of having a GitBash shell, namely to run git on the command line, ought not to require winpty |
Are you sure that you're running this in Git's Bash, not e.g. Cygwin's Bash? |
Don't have Cygwin installed. Opened GitBash from the Windows Start menu (opening with a right click from Windows Explorer is the same). Prompt contains MINGW64 |
Can you provide the (redacted, if necessary to hide secrets) output of |
|
Another hunch: does |
Still no displayed text |
Does |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
However, |
This comment has been minimized.
This comment has been minimized.
More information: Output is displayed with prerelease-v2.11.0.windows.1.1 (git version 2.10.2.windows.1.895.g8126884) released Dec 9, 2016 Output is not displayed on the next release: v2.11.1.windows-prerelease.1 released Dec 23, 2016 I've also tried installing 2.21.0 in VM running a plain vanilla Windows 7 - it works OK |
That is stdout.
And that is stderr. So it seems that stderr is suppressed, but stdout is shown. However, the original report stated that Which kinda contradicts each other...
Unfortunately the diff is pretty large: 118 files changed, 50942 insertions(+), 39137 deletions(-) Also, there were 1295 commits between those two revisions :-( Additionally, I just powered up my 2008R2 SP1 VM and launched a $ git version
git version 2.20.1.windows.1
$ cmd //c ver
Microsoft Windows [Version 6.1.7601] So I am really, really puzzled now. |
I have the same issue. Any clues on how to fix this? |
@sidchat04 for starters, could you try to pinpoint (e.g. by installing and testing the PortableGit) which Git version was the first one to break in your scenario. |
@dscho I tried installing the PortableGit, and surprisingly, the latest version seems to work as expected there. I uninstalled and re-installed the normal Git for Windows after this, but still facing the same issue. |
@dscho This gave me an idea, and I uninstalled and re-installed Git for Windows again. But this time, instead of installing at the regular "Program Files" path, I installed it in a different location. And it worked! I am still not sure what exactly is wrong, though. |
Oh wow! Good find. Now, what does this mean, though... ;-) Can you verify that calling |
It does show an output
|
Hmm. Is it possible that there is any |
Nope. I just checked. Another thing I tried, was to use the portable installation's exe from within the Program Files installation's Git bash, and it works as expected. |
Hmm. Can you recompile Git in a Git for Windows SDK? If you can do that, you could add some debug print statements so that we can find out in a more direct manner what is happening here. |
I was very happy with old git (git bash for windows) version, I can copy paste paths/commands and it shows output in console. Lately I updated my version to 2.29.2.windows.2. It doesn't show output for some commands and no copy-paste privilege. Found this thread. Bit new to software programming. Any help will be highly appreciated. |
@RammySekham how about opening a new ticket, providing a high quality bug report? |
Sure |
Setup
64-bit Windows 7
defaults?
to the issue you're seeing?
Don't think so
Details
Bash
Minimal, Complete, and Verifiable example
this will help us understand the issue.
The git version number to be displayed in the Bash terminal
No output displayed.
This seems to be the case for all git commands. Ordinary shell commands (such as ls, and less) output as expected
If I pipe the output to a file then the file contains the expected output, e.g.
If I force an error, for instance by changing to a directory that does not contain a git repository then the error message is displayed, e.g.
A colleague installed 2.20.0 on another machine and was getting a similar issue.
Running git commands from a normal command window gives the output expected
URL to that repository to help us with testing?
Does not appear to be repository specific
The text was updated successfully, but these errors were encountered: