On 2010-04-28 13:37 +0100, Óscar Fuentes wrote: > Leo <[email protected]> writes: > >> Hello, >> >> I personally feel the change to bind l to magit-log-show-more-entries is >> not a good change. Viewing more log entries is not a frequent >> operations. > > I do it often.
Good for you. Maybe you should consider increasing the default length. Anyway, the current way of implementation is not optimal. For example, when you are at the top of the log buffer, then hit 'l' (or whatever key), you have no cue of what happened. In fact I have the cut off length increased to 1600 without knowing it. >> Emacs 23.2 actually got it right, they put two buttons at >> the end of the log buffer so occasionally you can click on them if you >> want to get more entries. > > I tend to avoid clicking on things. Keyboard shortcuts are much more > convenient, IMO. 'click' was not the right word. I mean move the cursor to the button and hit RETURN. In most cases, it is a combination of TAB + RETURN. I don't see much of disadvantage here. Usually when you want to see more entries is when you move towards to the end of log buffer. Here is an example of how slime implements its function browser (inspector); vc does something similar. http://imagebin.org/94859 I would highly suggest magit does something similar. >> Secondly I quite like the old behaviour of typing 'l' to go back to >> short log list from the logs created by 'L' or 'H'. > > Maybe `l' was not the best shortcut. Once you have a keymap specific for > log buffers, there is plenty of available keys without removing existing > features. Some keys such as t/T is now missing in the log buffer. It seems t/T only allow tagging the HEAD. Is is possible to tag a commit? I.e. take the sha1 where the point is and tag it. Cheers, Leo -- H A P P Y H O L I D A Y S!
