Nikolai Weibull <[email protected]> writes: > When you want to push your commits you press P, then you consider if > there are any options that you want to specify. After having > considered this you press P again. > > When you want to commit your changes you press c, then you consider > what those changes are and write an appropriate message. After having > done this you press C-c C-c. > > Thus, for commits, the message buffer is your pause area. Here you > write your message, toggle options, and so on. For push, there’s no > buffer, but an options menu. > > Having these tasks be consistent in how they’re executed can actually > hurt more than it helps. Consider that you almost always will press c > c when you commit. You’ll soon develop a habit that can easily infect > your habit of pausing after P and just press P P without thinking > things through first.
The key-groups popup is not a "pause area" by any stretch. I press `ll' for `short log' all the time, `bb' for `check out', `ff' for `fetch' and... `PP' for `push' without pausing at all. If key-groups does anything on the "protecting users from their own mistakes" area is to require two key presses instead of one, that's all. If you are afraid of accidentally pushing your changes some other mechanism should be implemented. Actually, I share your concerns about accidental pushes (among other operations) and something like requiring to type a random string (let's say two letters) just before the command executes, is something I'll use. As an opt-in feature, of course. [snip] -- --- You received this message because you are subscribed to the Google Groups "magit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
