Error: Command failed: git log --pretty="format:{#/dquotes/id#/dquotes/:

[filjoseph1989]

when I install this package an error popup that says this

Select a file in the git repo to see timeline
application\controllers\Checklist.php83:1
CRLFUTF-8PHPchecklist+10, -11
Error: Command failed: git log --pretty="format:{#/dquotes/id#/dquotes/: #/dquotes/%H#/dquotes/, #/dquotes/authorName#/dquotes/: #/dquotes/%an#/dquotes/, #/dquotes/relativeDate#/dquotes/: #/dquotes/%cr#/dquotes/, #/dquotes/authorDate#/dquotes/: %at, #/dquotes/message#/dquotes/: #/dquotes/%s#/dquotes/, #/dquotes/body#/dquotes/: #/dquotes/%b#/dquotes/, #/dquotes/hash#/dquotes/: #/dquotes/%h#/dquotes/}" --topo-order --date=local --numstat C:\xampp\htdocs\my_project\application\controllers\Checklist.php 'git' is not recognized as an internal or external command, operable program or batch file.

what to do about that?

[rnarron]

Add wherever_your_git/bin to %PATH%

[filjoseph1989]

Ah see thanks a lot

[glassfordm]

In a workspace containing two project folders, one under git source control and one not, after I use git-time-machine on any file under source control, even if I then toggle it back off, opening any file that is not under source control also results in this error.

[paradox460]

I'm getting the same errors. My git binary is installed using Homebrew, and works pretty much everywhere else on the system. My homebrew directories are a part of my path

[littlebee]

@paradox460, Are you able to use git-log or git-history successfully?

[paradox460]

No, unfortunately :(

nikhilkalige/git-log#73 and jakesankey/git-history#34

[littlebee]

Hmm... do I release the new version without any new visible features, but with a complete refactor of how git log is accessed, as a minor or a patch?

I'm a little scared about how it will work on windows (I don't know, but nodegit which it uses via libgit2-log-utils) should work... 😨 If one of you guys has the will and skill and would pull the 'development' branch locally and try it out, that would be super helpful. On mac you just clone the branch to a local dir and then sym link it into ~/.atom/packages.

[paradox460]

I'm only on mac, but I might be able to coerce a colleague who uses windows
and knows git to test it out

On Thu, May 19, 2016 at 8:51 PM Bee [email protected] wrote:

Hmm... do I release the new version without any new visible features, but
with a complete refactor of how git log is accessed, as a minor or a patch?

I'm a little scared about how it will work on windows (I don't know, but
nodegit which it uses via libgit2-log-utils
https://github.com/littlebee/libgit2-log-utils) should work... 😨 If
one of you guys has the will and skill and would pull the 'development'
branch locally and try it out, that would be super helpful. On mac you just
clone the branch to a local dir and then sym link it into ~/.atom/packages.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#48 (comment)

[dennismphil]

I got this issue on my mac after upgrading to Mac OX Sierra. The issue got fixed after agreeing to the xcode licence agreement

sudo xcodebuild -license