Do we really need a shell for this? If you're reusing some of these so often, why not just alias them in your bashrc? The interactive shell requires way more key-presses than any of my aliases not to mention sticking me into a shell that I need to exit out of later to get back to my development environment.
$ cat ~/.bashrc | grep git
alias gitc='git commit -a -s'
alias gitls='git log --pretty=oneline'
alias gitb='git branch'
alias gitca='git commit -a --amend'
alias gits='git status'
$ cat ~/.alias
alias g='git'
$ cat ~/.gitconfig
[alias]
st = status
br = branch
co = checkout
I don't see anyone else doing g='git' but I don't have to write out an alias for each command. For less frequently used git commands I forget an [alias] shortcut but I can always use the 'g' shortcut.
$ cat ~/.bash_profile | grep git
alias gco="git checkout"
alias gpu="git pull"
alias gcom="git commit"
alias gfr="git fetch && git rebase -i"
alias g="git"
it actually looked nice imho before i realized it's one helluva slow ruby app(sorry, i like ruby, and considering i'm on a haswell laptop, i think i deserve to have my shell commands execute instantly).
unlike the hub command by github(doing different things) the gem dependencies/parsley are not trivial to combine into a single standalone version, so if i chose to use this i would have to install this weird structure of a ruby gem that is distributed as some kind of app that installs itself into usr/lib(most probably because rubygems would make the startup time even slower).
apparently there's also this https://github.com/rtomayko/git-sh which is just bash. but yeah i think i'll just stick with my aliases and tig.
EDIT: i don't know how i saw a /usr/bin/ruby shebang, but forget that part of the rant
Comments
Do we really need a shell for this? If you're reusing some of these so often, why not just alias them in your bashrc? The interactive shell requires way more key-presses than any of my aliases not to mention sticking me into a shell that I need to exit out of later to get back to my development environment.
If you want to keep bash completion on working when having git aliased to g, try to add this line to your .bashrc:
I was curious about this, so I checked: zsh will preserve completions if you `alias g=git`.
Yes, I use it too! Saves me a lot of time.
For people using oh-my-zsh, the git plugin has similar ones and quite a few more handy ones.
https://github.com/robbyrussell/oh-my-zsh/blob/master/plugin...
it actually looked nice imho before i realized it's one helluva slow ruby app(sorry, i like ruby, and considering i'm on a haswell laptop, i think i deserve to have my shell commands execute instantly).
unlike the hub command by github(doing different things) the gem dependencies/parsley are not trivial to combine into a single standalone version, so if i chose to use this i would have to install this weird structure of a ruby gem that is distributed as some kind of app that installs itself into usr/lib(most probably because rubygems would make the startup time even slower).
apparently there's also this https://github.com/rtomayko/git-sh which is just bash. but yeah i think i'll just stick with my aliases and tig.
EDIT: i don't know how i saw a /usr/bin/ruby shebang, but forget that part of the rant