Pierre Habouzit writes: > As you seem to be the guy to ask for, I've a couple of requests wrt > gitk. > > * the diff window is quite bad with merge commits, the colorization is > rather poor, and the last version you just merged isn't especially > better. That's not a request, that's a grizzle. :) What would you like it to look like? > * the 'sha1' input field is a major pain in the UI: the cut&paste > interaction is very poor. I don't know why, but it's often very very > hard to really copy the sha id, probably because it's selected by > default. It's selected so that the contents are in the cut buffer and you can paste them in an xterm with middle-button. Possibly I need to check that control-C (or command-C under macos) is properly bound to copy. > * the fact that it remembers the position where it was in the WM when > it was closed is really annoying. the WM is supposed to place the > window. With at least ion3 and xinerama it often shows up on the > wrong screen. Remembering the window size though is fine. That came in with some changes that make gitk start up correctly under windows. I could see about making it set the window position only under windows. > * still wrt the layout, the focus is quite cumbersome. Gitk would be > really really really nice to be used only from the keyboard, but > because of a very unclear focus policy, it really isn't for me. > Maybe it's just me, and I know this may not be 100% helpful, but I > never know which part of gitk will receive my keys (history part, > diff part, tree, ...). What focus policy would you like? Paul. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
