SlugFiller

I'm... not sure how. I know it's big, but it's all part of the same thing. I don't think I could even split it into several commits in any way...

@romanz Sorry for the delayed response. I wanted to be 100% certain about my answer. I'm rather unhappy with the changes you've mentioned. They were mostly hacked together to make...

No. You just put all the device stuff in a thread. There are three ways to handle the concurrent calls it would inevitably create. First, avoid them at the caller...

> Just to be sure - is the main issue cross-platform signal handling? It's not so much the signal handling itself. Rather, it's the lack of a way to wait...

Rebased on top of #456 and added support for deleting keys (requires `--delete-secret-and-public-keys`) I'm still contemplating extending derivation path setting to primary keys, and refactoring the way the derivation path...

@romanz Okay, I've had a thought about taking this PR in a completely different direction. And I want your opinion. Normally, GPG-agent is supposed to manage private/secret keys. It stores...

Since I didn't get any response in a while, so I decided to go ahead and implement key storage in `private-keys-v1.d`. Now it's possible to separately delete public or secret...

If you have one, you can simply enable the agent and test.

The best motivation for contribution is needing it, or knowing someone who needs it. Worrying about support for a device you don't have and don't know anyone who has is...

At a glance, it seems to be trying to run `pinentry`, and failing. It's not failing very gracefully, which is unfortunate (and will be fixed by an upcoming PR). But...