Closed
Description
Setup
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
$ git --version --build-options
git version 2.20.1.windows.1
cpu: x86_64
built from commit: 7c9fbc07db0e2939b36095df45864b8cda19b64f
sizeof-long: 4
sizeof-size_t: 8
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver
Microsoft Windows [Version 6.1.7601]
64-bit Windows 7
- What options did you set as part of the installation? Or did you choose the
defaults?
# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
> type "C:\Program Files (x86)\Git\etc\install-options.txt"
> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
$ cat /etc/install-options.txt
Editor Option: CustomEditor
Custom Editor Path: C:\Notepad++Portable\Notepad++Portable.exe
Path Option: Cmd
SSH Option: OpenSSH
CURL Option: OpenSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Disabled
- Any other interesting things about your environment that might be related
to the issue you're seeing?
Don't think so
Details
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
Bash
- What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
git --version
- What did you expect to occur after running these commands?
The git version number to be displayed in the Bash terminal
- What actually happened instead?
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.
$ git --version >> version.txt
$ cat version.txt
git version 2.20.1.windows.1
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.
$ git status
fatal: not a git repository (or any of the parent directories): .git
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
- If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
Does not appear to be repository specific