diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-06 02:31:13 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-06 02:31:13 -0600 |
| commit | 0ae5679aa160245af248836e1d7743aeff63f2e1 (patch) | |
| tree | 64608dccc9bfd57800995a414f6287b7605ca637 /kinit/README.wrapper | |
| parent | d3b5575f31f14629dbd3fd900665e1a69aa7bcd5 (diff) | |
| download | tdelibs-0ae5679aa160245af248836e1d7743aeff63f2e1.tar.gz tdelibs-0ae5679aa160245af248836e1d7743aeff63f2e1.zip | |
Additional kde to tde renaming
Diffstat (limited to 'kinit/README.wrapper')
| -rw-r--r-- | kinit/README.wrapper | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/kinit/README.wrapper b/kinit/README.wrapper index 48bfdc7e8..077d2b870 100644 --- a/kinit/README.wrapper +++ b/kinit/README.wrapper @@ -1,24 +1,24 @@ README -kdeinit_wrapper, kshell and kwrapper are a programs that -start programs via kdeinit. +tdeinit_wrapper, kshell and kwrapper are a programs that +start programs via tdeinit. E.g. You can make a symbolic link from $KDEDIR/bin/konsole to -$KDEDIR/bin/kdeinit_wrapper. Typing 'konsole' on the command line -will then start 'konsole.la' through kdeinit instead. +$KDEDIR/bin/tdeinit_wrapper. Typing 'konsole' on the command line +will then start 'konsole.la' through tdeinit instead. -kdeinit_wrapper is the simplest for, it only passes the program -and arguments to kdeinit, nothing else +tdeinit_wrapper is the simplest for, it only passes the program +and arguments to tdeinit, nothing else kshell is usually the best choice, it passes the program, arguments, complete environment ( $PATH, etc. ) and current -working directory to kdeinit +working directory to tdeinit kwrapper tries to make the program look like it was actually -really started directly and not via kdeinit. In addition to +really started directly and not via tdeinit. In addition to what kshell does, it also tries to redirect the program output to the console from which kwrapper was started, it waits -for the program started via kdeinit to finish and only after then +for the program started via tdeinit to finish and only after then it exits ( it doesn't return its return value though ), and it also passes most signals it gets to the process of the started program ( thus allowing you to break it using Ctrl+C or stopping @@ -31,8 +31,8 @@ TODO ==== * There is no portable way to read out the complete environment and - pass it to kdeinit. - kdeinit should probably unset every + pass it to tdeinit. - tdeinit should probably unset every variable that's not set in the environment it gets from kshell or kwrapper * stdout/stderr of the started application goes to the console where - kdeinit was started. - done, I hope it's ok + tdeinit was started. - done, I hope it's ok |