Closed oschrenk closed 11 years ago
Yeah. This is super annoying. It's because mv is using git-mv. The only way around it is to use command mv file1 file2
. You may also be able to realias mv to command mv
but I haven't tried.
I've considered removing the mv alias due to the confusion here.
Solution would be to test if file is tracked or not and act accordingly. As a workaround you can use noop
: && mv file1 file2.
The following lines in my .gitshrc make mv
/rm
a bit more sane, without any changes to git-sh
itself:
unalias mv
unalias rm
alias gmv='git mv'
alias grm='git rm'
Thanks for that!
There's a note about this in the README. Closing.
I've worked up a couple bash functions for .gitshrc that will route tracked files to git mv/rm and untracked files to their bash counterparts. https://github.com/phatblat/dotfiles/blob/master/.gitshrc#L66
I use
git sh
a lot these days to save me some keystrokes.When I want to move some untracked files though using
I get
Is there a workaround?