scmbreeze / scm_breeze

Adds numbered shortcuts to the output git status, and much more
https://madebynathan.com/2011/10/19/git-shortcuts-like-youve-never-seen-before/
MIT License
2.82k stars 191 forks source link

Don't show oldname -> newname for unstaged modifications #144

Closed zommerfelds closed 10 years ago

zommerfelds commented 10 years ago

If I take a file that is already checked in, named foo, from my working directory and run

git mv foo bar
echo 'new content' >> bar

then pure git status gives me

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

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

    renamed:    foo -> bar

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:   bar

and scm_breeze git status gives me

# On branch: master  |  [*] => $e*
#
➤ Changes to be committed
#
#        renamed: [1] foo -> bar 
#
➤ Changes not staged for commit
#
#       modified: [2] foo -> bar 
#

Note that on the modified: [2] line it looks like a rename, but it's only a modification, whereas on the original git it shows only the new file name. Would it be possible to have it like the original git? Also, this would allow us to run git add 2 without getting

# fatal: pathspec '/path/to/repo/foo -> bar' did not match any files

P.S. Thanks for the great tool!