On Saturday, 29 October 2005, at 08:17:01 (+0200), Sebastian Dransfeld wrote:
> Damn, I'm braindead. The point is when a process doesn't know > anything about the startup id stuff, and doesn't unset the env. So > my fix was faulty too. There should be something to identify an > exe'd process and unset the env variable if the process doesn't. A > pid check and a timer? Heck no. Once you exec the process, its environment is no longer yours to control. The bottom line here is that the system is imperfect because it's trying to create a relationship that X was specifically designed not to understand: processes and their windows (or vice versa). There is no perfect solution; accept that as given and move on. You can only do so much. One thing that might help is to unset the env var in your .bashrc/.bash_profile. But that only works for shell-based apps. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "It doesn't take a lot of strength to hang on. It takes a lot of strength to let go." -- Rep. JC Watts, Jr. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
