Better error reporting of GPG failures

[repli2dev]

I run into strange situation when my gpg via terminal worked (exactly the same command copied from the log) however the plugin failed to loaded with "Message could not be decrypted! (Press ENTER)".

The problem was in that the gpg worked but returned code 2 as it encounered on malformed GPG_AGENT_INFO variable and it would be really nice if I haven't spent two hours of gun-shot debugging to find this :-)

[jamessan]

Suggestions welcome. I don't think there's much information from gpg in such a situation (but don't have an environment to check right now).

[repli2dev]

Thanks for reply :-) In my situation changing the message "Message could not be encrypted! (Press ENTER)" to something like "Message could not be encrypted as gpg command exited with non zero code! (Press ENTER)" would be much more helpful.

Another idea would be to capture the error output and in show it in the case of failure (such as this). But that would be probably overkill as the first suggested approach seems to convey the main message where to look.