Bee via Gnupg-users wrote:
> In the mean time, you could put something along the lines of:
>
> {CmdCalls ; } 2>&1 | grep -v -e "^gpg: problem with fast path key
> listing: Forbidden - ignored$" or something, to keep that output out
> of your stderr stream.
I think there's a downside to that (but I could always be
wrong). Redirecting stderr to stdout would prevent mutt (or
whatever tool was using being used) from being be able to
display output only from stderr. That is helpful when the
exit status is 0 but there were warnings, as in this case.
> If something else unexpected displays, you'll get more issues, but
> then you probably want to know if / when / should that happen.
>
> If you add --quiet now, even when the change below happens later, your
> script above won't need to change again.
Indeed, if Werner weren't so quick, perhaps I would have
considered some sort of adjustment. Though I try to use the
mutt's contrib/gpg.rc unaltered so I don't have to remember
to merge in fixes they make there.
This does remind me that I should re-evaluate using gpgme
as the backend. I don't recall why I disabled that now. It
may have been for an issue which is long-since resolved. ;)
--
Todd
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
