Skip to content
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

eg status outputs nothing, with no error message #3

Open
roryokane opened this issue May 24, 2014 · 0 comments
Open

eg status outputs nothing, with no error message #3

roryokane opened this issue May 24, 2014 · 0 comments

Comments

@roryokane
Copy link

I suspect that this is because the format of git status has changed. It no longer puts # at the beginning of every line.

$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   index.html

Untracked files:
  (use "git add <file>..." to include in what will be committed)

    TODO.txt

no changes added to commit (use "git add" and/or "git commit -a")
$ eg status
$ 

I have “eg version 1.8.2.dev”, and “git version 1.8.5.2 (Apple Git-48)”. This also happens even with “git version 1.9.3”, and with Elijah Newren’s old EasyGit 1.7.5.2.

Here are some examples of git status in earlier versions of Git, for comparison:

git status in “Rerere Your Boat...” on the Git blog, posted 2010-03-08:

$ git status
# On branch master
# Unmerged paths:
#   (use "git reset HEAD <file>..." to unstage)
#   (use "git add <file>..." to mark resolution)
#
#   both modified:      hello.rb
#

git status in “Git Tip of the Week: Index Revisited” on a blog, posted 2011-10-18:

$ git status
# On branch master
# Changes not staged for commit:
#   (use "git add <file>…" to update what will be committed)
#   (use "git checkout -- <file>…" to discard changes in working directory)
#
#   modified:   example
#
no changes added to commit (use "git add" and/or "git commit -a")
$

I’m not sure that the changed git status is the cause, since eg status doesn’t even output an error message, or fail with a nonzero status code, even though I see that it has code that is supposed to do that upon an unsuccessful parse. It just completes successfully and outputs nothing. But I do see that eg has code to remove #, which is no longer in the git status output, so that is probably at least part of the problem.

EasyGit does its parsing of the output of git status around line 6558.

So you know what eg status is supposed to output, here’s a Stack Overflow question with example output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant