3 ms·
For some long and complex git commands I have aliases, also for command line options that I always want to provide. My ~/.gitconfig therefore is quite extensive
by wladimir 15y ago
For some long and complex git commands I have aliases, also for command line options that I always want to provide. My ~/.gitconfig therefore is quite extensive.
But I agree that using aliases for trivial, short commands such as these doesn't really help. Remembering the alias is more work then just typing the whole command.
Edit: why is jacques_chester's reply to this post killed!?
- deleted 15y ago[deleted]
- jacques_chester 15y ago> Remembering the alias is more work then just typing the whole command. I set up aliases like this myself (right down to the abbreviated name) and I find it no more difficult to remember. Just much faster. For the same reason I've aliased 's' to 'sudo' on some servers, and I've alised complicated ssh connections to short names like 'blahweb' and 'blahdb'. Sure, I can remember what they stand for. But I'm impatient and want to spend finger cheese on more useful characters.