NOTE: this email only addresses key-binding issues, not the potentially
more serious emacsclient issues which both appear in this thread.
Óscar Fuentes <[email protected]> writes:
> Eric Schulte <[email protected]>
> writes:
>
>> Fair enough. While I disagree that pressing command keys twice is
>> negligible, and I spend no where near several minutes writing my commit
>> messages, we probably just have different commit styles.
>
> It takes at least several minutes to create the changes that you plan to
> commit. Writing the commit message is just a final chore.
>
>> Perhaps a workable middle ground acknowledging such personal differences
>> would be to introduce a variable (say `magit-immediate-commands') which
>> controls which commands run immediately by default, and all other
>> commands could open the option dialog.
>
> IIRC there was an "old-magit compatibility special mode" for those who
> disliked key-groups. Maybe it was removed, dunno. I'm fine with your
> proposal as long as it is opt-in. After all, I will not use it nor I had
> to maintain the code ;-)
>
It *is* opt in as you have to customize `magit-immediate-commands'
(which could be set to `nil' by default) to use it. The maintenance
burden of ~15 new lines in `magit-key-mode-generate' should be nil.
While this is certainly not the most important issue, I think the
ability to avoid pop-up menus for very common actions is worth the extra
configuration variable.
Cheers,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
--
---
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.
