Re: New features in gitk
- From
Jonathan del Strother <maillist@steelskies.com>
- Date
- Oct 29, 2007, 08:31 UTC
- Message-ID
- <8E362637-5AE6-43DC-890D-78BC6B43BDA1@steelskies.com>
- In-Reply-To
- <20071029062000.GB4310@artemis.corp>
On 29 Oct 2007, at 06:20, Pierre Habouzit wrote:
Show 23 quoted lines
> On Sun, Oct 28, 2007 at 11:13:43PM +0000, Paul Mackerras wrote: >>> * 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. > > Well, doing ^C doesn't always copy it (probably a glitch wrt which > input has the focus), and it certainly doesn't synchronize with the > cut > buffer for me. And it doesn't work for anyone at work either. I use > ion > with the KDE clipboard manager (klipper -- because I never managed to > find a clipboard manager that is as good yet, not depending upon KDE), > and at work most people use KDE, with the same klipper. Maybe it's > a bad > interaction, I should try to use it under gnome or so to see if it is. >
FWIW, I have exactly the same problem under OS X. I've never figured out a pattern that gives a guaranteed copy - I'll try playing around today and see what I can find.
Actually, while I'm here, gitk semi-regularly ignores ⌘Q, which ought to quit on OS X.