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. On a different topic: do most folks bind 'magit-status' to a simpler key sequence? I just did my first commit with the new work flow after fixing my Mac issue. I assume there is good reason for all the changes (and I'm not trying to be sarcastic) but I'm having some growing pains right now. On a different different topic: emacs + git + magit is wonderful! Really. It just feels so nice in so many ways. Perry
signature.asc
Description: Message signed with OpenPGP using GPGMail
