5 Posted by Woody Peterson on 11 May, 2012 07:10 PM
Not that it's anyones problem but mine, but I already have a
global shortcut for this key combo (plus it's extra keys to press).
Is there a use case for the current behavior of ctrl-c that copies
the whole card in... json, is that what it is? Would it be
reasonable to allow users to have the normal command-c work as this
page suggests? This is how keepassx works, and I noticed that the
windows 1password has the equivalent behavior (plus double-copy
copying the username, which is cool).
So: why the divergence in the Mac client, and is there any way
(now or planned) to have password copying be the 'normal' copy
Support Staff6 Posted by Kyle Swank on 11 May, 2012 07:16 PM
Thanks for taking the time to contact us with your question.
As the decision to which keyboard shortcut we use was determined
far beyond the time I started here I couldn't give any clues as to
why it was chosen this way.
I, personally, would like to see some changes to this, but I'm
not sure how exactly we'd do this to make it obvious. The trouble
comes from what CMD+C copies. Does it copy the username? the
password? The obvious choice would be the password, but CMD+C
typically binds to whatever is selected and in this case nothing
would be selected (except for the whole item).
I know we are working on a major update to 1Password. This is
certainly something we can take a closer look at in this next
version to see what we can do to improve.
I know this doesn't give you a lot to work with, but I do want
you to know your voice is heard. Hopefully the next version will
make some changes here that make many of our users happier.
7 Posted by Woody Peterson on 11 May, 2012 08:41 PM
Thanks for the quick reply! I was mucking around with OS X's
application shortcuts menu just now, and it turns out you can
assign a shortcut to any menu item by exact name. I tried mapping
command-c to "Copy Password" and it worked! So, problem solved