Stdout is empty on Git log command

[oric01]

• node 4.4.0
• shelljs 0.7.0
• windows 7, using git bash

Using shelljs to stdout Git log does not work (in grunt file currently).

var shell = require('shelljs');

console.log(shell.exec('node -v'));

Works, console stdout : stdout: 'v4.4.0\r\n'

console.log(shell.exec('git log --no-merges --pretty=medium HEAD^...HEAD'));

Does not works, Works, console stdout : stdout: ''

While this Git log works in Git bash :

$ git log --no-merges --pretty=medium HEAD^...HEAD
commit be9a8bca6783f9911f0601afa00203f9a161ffd9
Author: xxx <xxx.xxx@xxx>
Date:   Tue Apr 26 17:02:47 2016 +0200

    feat(streaming): XXX : XXX

    - change 1
    - change 1

[nfischer]

@oric01 do other git commands (like git status) work? Also, what is the output on the terminal when you redirect stdout?

$ git log --no-merges --pretty=medium HEAD^...HEAD >file.txt

Just want to verify that the git log command really is going to stdout for you and not stderr.

[oric01]

@nfischer It's strange... now when i run shelljs, git command is unknown... while it's still running on git bash.
I'm a bit confused, it was at least running git command correctly until now.
FYI, I installed git bash the way it's not available in cmd.exe, but as far as I understand, it should'nt be a problem.

Previously the returned code was 0 with just stdout empty (on git log) and I also finally noticed that shelljs was running cmd.exe so I was waiting for #330 to be fixed, but my problem still remain.

[nfischer]

It has to be part of your path to use it. Exec spawns a new cmd.exe. Please add the git binaries to your path first to take advantage of them via shelljs.

[oric01]

Is there a way that shelljs use bash instead of cmd.exe ?
Currently im using git bash to have a "unix like" shell so I can run the same scripts between local env (window) and dist env (linux) for grunt build scripts ie.

[nfischer]

Yes, you need to use the {'shell': '/path/to-bash.exe'} argument to exec. That may work nicely for you. Find whatever the path is to your bash executable of course and past that in there, remembering to properly escape any backslashes and whatnot.

[nfischer]

@oric01 Here's the exec docs, which point to the page for the child_process module. Any option in that module's exec should be supported here as well, including shell.

[nfischer]

@oric01 I'm going to close this, since it looks like it was an issue with git being outside of your normal PATH, and that using {shell: 'path/to/git/bash.exe'} should fix it. Please reopen if this doesn't resolve the issue.

[oric01]

I tested with shell option but it's a pain to configure on windows...
I finally tested git status and it works...
Looks like it's related to the way git log is not flushed.
I continue to investigate...anyway thx for your support.