Keepassxc: Is there a way to get CTRL+V autotype back?

Created on 21 Apr 2019 · 8Comments · Source: keepassxreboot/keepassxc

I loved this shortcut and made a whole lot of sense but I see that you guys changed it just because a couple of people complained. Is there a way to get it back?

Expected Behavior

Hitting ctrl+v should execute autotype.

Current Behavior

Nothing happens.

Possible Solution

Right now ctrl+shift+v produces the expected behavior.

Steps to Reproduce

press ctrl+v on an entry
nothing happens

Context

On 2.3.4 hitting ctrl+v on an entry performs autotype as expected but for some reason on 2.4.0 and 2.4.1 the behavior changed.

Debug Info

KeePassXC - Version 2.4.1
Revision: 7bafe65

Qt 5.11.3
Debugging mode is disabled.

Operating system: Fedora 29 (Twenty Nine)
CPU architecture: x86_64
Kernel: linux 5.0.7-200.fc29.x86_64

Enabled extensions:

Auto-Type
Browser Integration
SSH Agent
KeeShare (only unsigned sharing)
YubiKey

Cryptographic libraries:
libgcrypt 1.8.4

Source

rpgdev

Most helpful comment

@wolframroesler indeed. I don't know why, instead of just replacing the shortcut, they didn't make it configurable with their new beloved default value ctrl-shift-v.
I'm still using 2.3.3 to have that shortcut.

seguri on 24 May 2019

👍3

All 8 comments

It's not just a "couple of people complaining". We removed it after careful deliberation, since it is dangerous (we ourselves even keep fat-fingering that shortcut every now and then) and it does NOT make a lot of sense. Ctrl+V is paste, not "minimise window and start typing where ever that has left you". I do acknowledge that people got used to it and are upset about changes, but there is really no reason why you couldn't get used to Ctrl+Shift+V instead.

There is no way you can change it back and we do not have any plans to bring it back.

phoerious on 21 Apr 2019

👎1 👍1

There is no way you can change it back and we do not have any plans to bring it back.

That's what I thought but for the saque of the argument:

it does NOT make a lot of sense.

Yes it does, if it didn't you wouldn't have selected it as the shortcut for autotype in the first place. Autotype "pastes" your credentials where you need them. In the context of this application ctrl+v for this functionality made sense.

I do acknowledge that people got used to it and are upset about changes, but there is really no reason why you couldn't get used to Ctrl+Shift+V instead.

It's not the same to type ctrl+something than ctrl+SHIFT+something. At least you could've selected another, two key combination.

rpgdev on 21 Apr 2019

👍1

We did not select this shortcut to begin with, it was in the original application that we forked from. The point of the change is to make sure the key combo is intentional. Adding the shift key makes it intentional since it is not a "normal" action.

droidmonkey on 21 Apr 2019

👎1

Ctrl+V ON KeePassXC is to paste something INTO KeePassXC. This is a conflicting shortcut.

phoerious on 21 Apr 2019

👎1

Ctrl+V ON KeePassXC is to paste something INTO KeePassXC. This is a conflicting shortcut.

I understand that but that has always been the case and yet you still chose ctrl+v as the autotype shortcut and the reason you did it was because it made sense. You changed your mind, and I accept this, but the shortcut still makes sense.

rpgdev on 21 Apr 2019

We did not and we did not change our minds. We left it as is and now we changed it.

phoerious on 21 Apr 2019

👎1

How about making hotkeys configurable, thus finishing the discussion once and forever? (I also strongly want ctrl-V back BTW, because I found it both convenient and intuitive, and because I have to twist my wrist in in uncomfortable way to type shift-ctrl-V which makes using it just that little bit unpleasant.)