Dominik Schulz

@BoostCookie `clear` is launching another instance of gopass in the background. It will wait for the specified timeout and then erase the clipboard - but only if the content (hash)...

This issue is very old and I haven't seen recent reports about this. Closing this for the time being. If new issues arise please open new issues.

No progress and lot's of failing tests. I'm going to close this here, but feel free to re-open once you have addressed the open comments and fixed the tests.

At first sight this looks like two separate issues. Parsing the git version should affect how configs are read since git config parsing is implemented in Go w/o calling out...

That is correct. This path does certainly not exist on Windows.

I don't think there is anything we can fix here. Handling the first line of a secret as the password is coming form the pass format and we don't want...

Yes, I'm sorry. Please see https://github.com/gopasspw/gopass/issues/2728

There is a potential pitfall: key trust. For historical reasons the gopass CLI defaults to `always trust` while the integrations do not. This should only matter during encryption and I...

These error messages are very annoying indeed. We can certainly try to provide more context, if we have it.

At this point I don't see how we could easily provide more context. We're just calling into gpg and that does that rest.