On Thu, Aug 29, 2013 at 09:57:38AM -0500, Perry Smith wrote: > On Aug 29, 2013, at 8:52 AM, Adam Spiers <[email protected]> wrote: > > On 27 August 2013 14:40, Phil Jackson <[email protected]> wrote: > >> Hey all, > >> > >> When I wrote the current menu-popup system in Magit I implemented > >> a popup for commiting just like the one that's been built > >> here. People were generally happy with the popup menus elsewhere > >> but I pulled it out of commit because there was so much > >> resistance. > >> > >> Before I quit Magit I had intended to keep the current workflow > >> but have a slightly nicer implementation of the > >> header-for-options system that served us reasonably well for all > >> this time. > >> > >> My two cents; I'm not sure I like the new way. I find the menu is > >> obstructive in this instance. > > > > Agreed Phil. The most common commit use case by far is surely "commit > > without needing any special options", so to always pop up a menu > > offering options is suboptimal for the majority of cases. Presumably > > this is why there was so much resistance when you first introduced it. > > But this could be said about most of the operations. "P P" to push. "F F" > to pull.
I disagree - e.g. I *always* want to pause and think before issuing a push. Allowing push via a single keystroke is far too dangerous. > On a different topic: do most folks bind 'magit-status' to a simpler key > sequence? Yes, C-S-g here. > On a different different topic: emacs + git + magit is wonderful! Really. It > just feels so nice in so many ways. Agreed! :-) -- --- 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.
