Comment by zahlman
2 days ago
FWIW, you can pretty easily script this sort of thing. In Bash it can even be a function added to your ~/.bashrc .
2 days ago
FWIW, you can pretty easily script this sort of thing. In Bash it can even be a function added to your ~/.bashrc .
Of course we already have it automated in pre-commit checks, I'm just mildly annoyed that it's two different commands in the first place (though I'm sure there is some good historical reason). The distinction/ordering between them isn't really clear as a user, I just want "find and fix everything you can, error if you cant autofix" every time.
Just so you know, when people say "I hate this paper cut", they aren't really asking how they can put in extra work to get around it. Obviously hey can add some alias to ~/.bashrc... on every computer he uses. The complaint is that he has to do that in the first place. It's still annoying.
I prefer having things this way, because it respects the fact that I may have a different idea from the next person about how the pieces should be put together.
OK and the vast majority of people excluding you and them probably have a very close-or-nearly-identical idea about what should happen. So everyone can be happy, there's nothing being lost here.
You can align it by hand, if you want.
no one is proposing removing the sub-commands, only adding a shortcut that calls both