I like this kind of articles, we can get some ideas.
From your examples, I had the feeling that you're not sure how to include arguments or bash commands into aliases. You might be interested in one my articles:
I do know. And the comments taught me a good deal but I don't like adding bash commands to git aliases since I use git on non Linux machines
Sorry then. How come you use sed and xargs in your aliases? Or you want to maintain only one .gitconfig and push all the rest to OS-specific setenvs?
sed
xargs
.gitconfig
That's it!
I write completely different aliases for Powershell but I get to still use identical git aliases
Have you considered using Git BASH on windows?
yep, quickly dismissed it. It's not worth it plus Powershell is just so damned good!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like this kind of articles, we can get some ideas.
From your examples, I had the feeling that you're not sure how to include arguments or bash commands into aliases. You might be interested in one my articles:
How do you prepare your commits?
Sandor Dargo ・ Jul 3 ・ 5 min read
I do know. And the comments taught me a good deal but I don't like adding bash commands to git aliases since I use git on non Linux machines
Sorry then. How come you use
sed
andxargs
in your aliases? Or you want to maintain only one.gitconfig
and push all the rest to OS-specific setenvs?That's it!
I write completely different aliases for Powershell but I get to still use identical git aliases
Have you considered using Git BASH on windows?
yep, quickly dismissed it. It's not worth it plus Powershell is just so damned good!