On Fri, Aug 30, 2013 at 8:41 AM, Rémi Vanicat <[email protected]> wrote: > Óscar Fuentes <[email protected]> writes: > >> Seriously, I can't see what's so inefficient with pressing an extra `c' >> for committing. Two tenths of a second for an operation that culminates > e> a task that typically takes a minimum of several minutes? C'mon! > > I agree with this. I like the flexibility of the key-group as they are > now. And what is the matter with 'c c'? it only one key, and the same > one...
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. If, however, we’re set on using the new commit workflow of invoking git-commit immediately and using emacsclient, then this whole discussion is moot, as we’ll have to be able to specify options before we begin, rather than during/after. -- --- 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.
