ryran
commented
9 years ago Pyrite's advanced gpg options in preferences is greyed out. Is that because this feature is not enabled yet?
Indeed. I haven't taken the time to enable any of that.
I keep a keychain on a separate, encrypted drive but even setting the env variable GNUPGHOME does not work for Pyrite or in emacs. I don't get why this does not work,since Pyrite is invoking gpg(2) on the backend.
From what you're saying, it sounds like pyrite's python code isn't passing the environment variable on to the gpg process it spawns. I'll see if I can cobble together some time to either enable that or the advanced preferences page.
Submitted via email.
Hi Ryan , first thanks for your contribution. So one thing I noticed is Pyrite's advanced gpg options in preferences is greyed out. Is that because this feature is not enabled yet? It would be nice if it was so that I may be able to change my gpg home dir to something else. I keep a keychain on a separate, encrypted drive but even setting the env variable GNUPGHOME does not work for Pyrite or in emacs. I don't get why this does not work,since Pyrite is invoking gpg(2) on the backend. Any clues or workarounds for what I wish to do? Mind you, changing my gpg path from .gnupg to something else via the GNUPGHOME variable works fine, so long as I issue gpg commands from the cli. Thank for your help :)