3 kdeinit4_wrapper, kshell4 and kwrapper4 are programs that
4 start programs via kdeinit4.
6 E.g. You can make a symbolic link from $KDEDIR/bin/konsole to
7 $KDEDIR/bin/kdeinit4_wrapper. Typing 'konsole' on the command line
8 will then start 'konsole.so' through kdeinit instead.
10 kdeinit4_wrapper is the simplest form, it only passes the program
11 and arguments to kdeinit, nothing else
13 kshell is usually the best choice, it passes the program,
14 arguments, complete environment ( $PATH, etc. ) and current
15 working directory to kdeinit
17 kwrapper tries to make the program look like it was actually
18 really started directly and not via kdeinit. In addition to
19 what kshell does, it also tries to redirect the program
20 output to the console from which kwrapper was started, it waits
21 for the program started via kdeinit to finish and only after then
22 it exits ( it doesn't return its return value though ), and
23 it also passes most signals it gets to the process of the started
24 program ( thus allowing you to break it using Ctrl+C or stopping
25 it using Ctrl+Z ). The drawbacks of this are that you'll have one
26 more process running, and also the signal passing and output
27 redirection may not work 100% reliably
33 * There is no portable way to read out the complete environment and
34 pass it to kdeinit. - kdeinit should probably unset every
35 variable that's not set in the environment it gets from kshell or
37 * stdout/stderr of the started application goes to the console where
38 kdeinit was started. - done, I hope it's ok