#include <hallo.h> * Dan Jacobson [Wed, Jul 12 2006, 04:10:36AM]: > Package: icewm-common > Version: 1.2.25-1 > Severity: wishlist > File: /usr/share/doc/icewm-common > > In the documentation and FAQs there are several examples of starting > icewm as the last thing in one's .xsession file.
That's the usual method. It guarantees that the critical application is icewm-session and the termination of .Xsession depends on it. But... > I found I needed to do > icewm-session& sleep 6 > bla bla& > bla bla& > wait ...this is also an interesting method, it helps starting the applications under WMs control. However I do not like it for two reasons: - it uses a hardcoded sleep period. My work machine needs definitely less than 6 seconds in the average case why should I wait? Or wha happens when it takes longer? - wait without argumentr waits for every PID. Maybe you just want to catch the PID of icewm-sesion with $! and wait for this only. Do you agree so far? No matter how, I think the better solution would be using the .icewm/startup file. Have you tried using it? What are the disadvantages for your scenario? > Also mention how the "exec icewm-session || exec xterm -fg red" Yeah, that line sucks. Once exec is executed, you can forget the return code handling (eg. || other stuff). I have just submitted it to the upstream BTS. > example will reach yyy when > $ cat eg > exec blabla || echo oooo > $ sh -x eg > + exec blabla > eg: line 1: exec: blabla: not found > I.e., Say if .xsession is different than a normal shell script. But .xsession is a normal shell script. > Also in /usr/share/doc/icewm-common/README.Debian.gz > Example .xinitrc file: > say if this is a sample .xinitrc / .xsession file, or also give a > sample .xsession file > #!/bin/sh #useful in .xsession? It does not hurt either. > add at least an xterm& here. > > exec /usr/bin/icewm-session Maybe. Are you happy with the suggestions on http://sourceforge.net/tracker/index.php?func=detail&aid=1520849&group_id=31&atid=100031 ? > P.S., the GNU address is no longer on Temple Place. Ok, reported, thanks. Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
