Óscar Fuentes <[email protected]> writes: > Rémi Vanicat <[email protected]> writes: > >> David Abrahams <[email protected]> writes: >> >>> At Thu, 13 May 2010 17:02:14 +0100, >>> Philip Jackson wrote: >>>> >>>> At Thu, 13 May 2010 09:48:02 -0600, >>>> David Abrahams wrote: >>>> >>>> > I often find myself launching GitX (http://gitx.frim.nl) on my mac >>>> > so I can get a view of how my branch relates to other ones. Usually >>>> > I just use the all branches option, which shows me everything >>>> > including the (known) remote branches. There are other useful >>>> > options that filter out parts based on remote, etc. It would be >>>> > awesome if we could do that from within Magit. >>>> >>>> That's not what 'V' almost does, right? >>> >>> No, V just lists the branch heads. I'm interested in something like >>> what `l' does, except showing all the known branches in the DAG. >> >> C-u l --all RET RET seem to do it, > > This is accidental, isn't it?
yes but it prove that we are very near to have it. > For me, it starts with 2000 lines of junk > like this: > > Commits at undefined > undefined > master~188 > undefined > master~655 > undefined > master~1021 > undefined > master~75 This is the list of the refs used to built this log view... May be we could use something shorter. > > [snip] > > The feature seems straightforward to implement but, once again, the most > problematic point is the key binding. What was the final resolution > about the proposal of prefixing every command with a key? (this one > could be `l a' for "log --all") And about grouping the commands into > sub-menus? It seem a good idea l a -> log all l l -> log current l RET -> same l L -> long log l h -> reflog l H -> the other reflog another idea would be to let "l" for simple log, and add the others after "L" -- Rémi Vanicat
