On Fri, 26 May 2017 09:06:08 +0900 Carsten Haitzler (The Rasterman) <[email protected]> wrote: > > ummm no. the parent process has already removed the env var before > your pinentry process is run. i read the gpg-agent code... i believe > it's that that spawns the pinentry... so the env var is already gone > before your process even begins to run.
Then you know the ENV variables are gone and not an option. > your only chance is to get it from arguments. this is why i said that > gpg in this case is simply creating extra work by passing as an arg > rather than as an env var which is what the rest of the "world" does > (your environment determines how to display - both for x11 and > wayland). I am not sure what their plans are, but this does not seem to be a problem for at least gnome, and maybe gtk pinentry. Those seem to work on Wayland with things how they are now. I am not sure how qt will address the issue. > elm may not init x in elm_init. it may init it later (e.g. when the > first window is really created), so don't depend on it being > explicitly initted in elm_init. just as long as by elm_init (and > after) DISPLAY env var is set... There is no ENV variable. One will not be set. -- William L. Thomson Jr.
pgpK1_4IIe3jQ.pgp
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
