On Tue, Jul 6, 2010 at 5:02 PM, Óscar Fuentes <[email protected]> wrote: > Nathan Weizenbaum <[email protected]> > writes: > >> How does this key-grouping system work? How would extensions fit into that? > > The idea is to have a key for each group of conceptually similar git > commands. There is `l' for all log-related commands, for instance. When > you press that key, a menu showing often-used command variants (short > log, long log, reflog, etc) and options (--grep, --all, etc) is shown. > > This doesn't go against having single keystrokes for some features, like > `$' for showing the git process buffer. However, if you are providing a > set of related and/or configurable features, integrating it with the > key-groups system would be nice for your users and relieve quite a bit > of nasty work from you. And it is very simple too: just add one item to > the `magit-menu' list for each command and option. > > The key-groups feature is conceptually finished. It just needs some > polishing on the implementation (I'll try to do it today) and after that > it is just a matter of adding items to the list that contains the menu > structure. So far it only contains log-related and branch-related > features for demo purposes (but even so it greatly improves the feature > set provided by stock magit, mostly for `log')
sounds great ! So if I understand correctly, there would be no required modification for the way git-svn works for example (as it already has the 'N' prefix). To make it play nice with extensions, one possibility would be to define this prefix at extension level, so I don't expect any problem there.
