On Thu, 25 May 2017 22:32:20 -0400 "William L. Thomson Jr." <[email protected]> said:
> On Fri, 26 May 2017 10:50:02 +0900 > Carsten Haitzler (The Rasterman) <[email protected]> wrote: > > > then stop going on with your mails and take the very first advice > > given if you don't care why. follow it and don't keep discussing the > > issue. if you want a discussion then that's fine but don't actually > > continue with the discussion and say "i don't care (what you have to > > say)". > > Advice given is not a solution. Problem remains. did you try it? > > you did keep digging for another solution even though one was > > presented already... what do you expect when you start digging > > deeper? you'll get more details! > > It does not work. GPG is not going to modify its behavior for EFL. This > is not an issue for others, at least gnome and likely gtk as well. you didn't read. > I personally care less if pinentry EFL works on Wayland. Day by day I > have less and less interest in Wayland, and its land of problems... > > > i gave you the very simple solution to set the env var with the > > string you already had parsed (well pinentry parsed it for you and > > stuffed it into a struct) and putenv() that. the very first thing i > > advised was to do that. you keep trying to look for other ways of > > doing it. > > If that will work for both X and Wayland I will go with that route. I > thought wayland used WAYLAND_DISPLAY not DISPLAY. i explained that already. go back and read. i told you what gpg-agent was doing and how environment variables are inherited. > > we do have the tools. gpg/(gpg-agent) specifically mess with how this > > normally works (99.9999% of the time). they explicitly remove the > > information from the environment that tells us how to display. they > > move it to a cmdline argument which means it creates work for you > > since the information is no longer in its normal location (an env > > var). you can do that work, just do it as i originally described. we > > don't need to provide any new tools. everything you need is there. > > it's the gpg guys that have forced you to learn about setting env > > vars that you would not need to know otherwise (if they set them > > before launching pinentry) and things would "just work". > > They are likely doing this for a reason. they do not have a good reason. as someone who knows how x, wayland, environment variables etc. work they do NOT have a good reason to pass as an ARGUMENT instead of as an env var. they give a reason - the client may have a different display than the gpg-agent - so sure. pass it on. but then set the env var before exec()ing the pinentry (in the agent). > > i could explain why env vars are the "right way" but given your > > current responses to help and information, i suspect you'll imply i > > should shut up by saying "i don't care", so just take the first > > advice given unless you are willing to have a discussion and learn > > something as a result. or do whatever you want. it's your code. > > Many times the right way is subject to opinion. > > -- > William L. Thomson Jr. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ 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
