On 29/10/15 16:13, Mike Blumenkrantz wrote: > I am not sure what you mean, but DISPLAY is not set when it is initialized > in this commit. >
Then I misunderstood your commit message. I thought the problem was that Pulse checks for "DISPLAY", and if it sees it's set it does all of what you've described, thus causing the lock. This made me suggest you unset DISPLAY before initialising pulse, so it thinks it's not in an X11 environment. My points are still valid though, we need to find a better solution, as the recommendations in the README are very unlikely to reach end users. Heck, it would possibly even be better to check if the module is loaded (or going to be?) and then act appropriately (like not initialise pulse or whatever is needed). I don't know E as well as you do, but telling users they need to load a module in a README and not forcing it, when if they fail to follow they get a locked environment doesn't sound like the best solution possible. -- Tom. > On Thu, Oct 29, 2015 at 8:07 AM Tom Hacohen <[email protected]> wrote: > >> Wouldn't it just be cleaner to unset and the set back DISPLAY around >> where you initialize pulse? The "TLDR" in the readme will probably never >> find its way to the users who will just complain/swear (and rightfully so). >> ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
