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 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. > * 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. > * c-u always forces a pop-up (for command discover-ability) Definitely some work to do here. > * 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. At least we're moving in that direction. 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). > * 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? Regards, Mosu
signature.asc
Description: This is a digitally signed message part.
