@werner Given you filed it as low priority and documentation - could you give feedback on whether that is expected behaviour or not?

@werner That begs the question: why can't quick-add-key re-use the same code that quick-add-uid is using?

I should have :) Thing is - a fix could be made in a backwards compatible way. So I don't really see your point.

And FWIW: an inconsistent UI/CLI should be treated as bug - not as a feature request.

You completely ignore the fact that --quick-add-uid and --quick-add-key are not consistent.
It's not clear why one should require a fingerprint and the other allows the kind of "user-id" you just described.
That was the main point of this issue.

From the man page:

--quick-add-uid user-id new-user-id
--quick-add-key fpr [algo [usage [expire]]]

To clarify: I would like to see the targeting of keys be unified.
I see the following options:

The matching error message and the similar keywords let me to miss that - indeed.