At Fri, 10 Dec 2010 11:44:36 +0100, Moritz Bunkus wrote: > > Hey, > > On Tuesday 07 December 2010 22:42:00 Dave Abrahams wrote: > > > I think the best answer is a hybrid (and it might be where we already > > are -- nobody's talking about pop-ups for `s', are they?): > > I like this proposal -- all the points you've made.
:-) > Now we have to agree upon the most-used actions that warrant single-tap > keys. My personal list would be: > > stage, unstage, commit, kill I'd like to add snapshot to that list. Just to be clear: when you say "single-tap" do you mean a key with no modifiers? Should we consider the set of single-modifier plus single-key combinations like `S-u' as an additional category? I ask in part because I'd also like stash to be really easy, but perhaps not as easy as snapshot. > I'd rather 'log' stayed at 'always popup', but I'd be OK with it being > converted back to a single-key action. I'll just re-map the key myself > then. I'm OK with it either way. > > * the user can modify the bindings of those keys (from 3 above but is > > there anything to implement? Users can already bind keys) > > Nothing to implement here, I'd say. I only raised it because it was in Phil's suggestions. I was wondering if he had something else in mind. > > * c-u always forces a pop-up (for command discover-ability) > > Definitely some work to do here. A trivial effort, though, right? > > * within pop-ups, double-taps invoke the most common command (from 2 > > above. Hey, once you have pop-ups, you might as well have a > > rationale for choosing the assignments within the pop-up, right?) > > I think the rationale is mostly to use the option name's first > letter as the accessor key with the exception of the most commonly > used option. That's not what I meant by a rationale; I see that as more of a convention. The rationale for that convention would be something like "it's more mnemonic that way." > At least we're moving in that direction. That's only after `-' or `='. I think the common convention for what to do is a little more complicated than your statement, but I don't have any argument with the general direction in which it is headed... I just think we should add the one change that the most common command is a straight double-tap. > When the key menus were first implemented the bindings were often > chosen to match the old single-key presses (e.g. 'V' in the branch > key menu would open the branch manager because it was bound to 'V' > before). Yes. > > * Uppercase keys invoke the more-destructive version of the command > > (e.g. `F' for pull vs. `f' for fetch) > > Fine with me. Would you change 'k' to 'K' then as well? No, I would reserve 'K' for a stronger form of kill, e.g. "kill without prompting for confirmation." -- Dave Abrahams BoostPro Computing http://www.boostpro.com
