Wish list: 10 improvements for KDE 4.2

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Reading and Writing a conf file - Suggestions and improvements?

Hello all As part of my TUI - (line based) Text User Interface, i do have 2 commands to assist working with conf files. Now, for me they work, but since i wrote them, i automaticly use them they way they should be used... you know what i mean. ;) Anyway, they are designed to read 'simple'...

2. UNIX for Dummies Questions & Answers

How To...KDE on Solaris 8

I have my shinny new SunFire 280 server with a fresh copy of Solaris 8 installed. I installed the options CD which includes KDE. I can't seem to get it to work. (This is what happens when management gives a Unix box to an x86 Network Admin and says "Figure it out" ) I have played with Mandrake and...

3. UNIX Desktop Questions & Answers

Kde 3.0

Hello, i,ve installed suse with kde 3.0, I had never used an X for unix before. So I don't know much. Most things were easy to find, but what anoyes me a lot is that the desktop is larger than mij monitor, so I have to move my mouse to see the rest of the desktop. I've tried to set the...

LEARN ABOUT SUSE

kdeinit4

KDEINIT4(8)							 KDE User's Manual						       KDEINIT4(8)

NAME

       kdeinit4 - Start all other KDE programs and kdeinit loadable modules (KLMs).

SYNOPSIS

       kdeinit4 [--help] [--no-fork | --no-kded | --suicide] [+programs | programs]

DESCRIPTION

       kdeinit4  is  a	process  launcher somewhat similar to the famous init used for booting UNIX. It executes KDE programs and kdeinit loadable
       modules (KLMs) starting them more efficiently.

       Using kdeinit4 to launch KDE applications makes starting a typical KDE application a couple times faster and reduces memory consumption	by
       a substantial amount.

       kdeinit4 is linked against all libraries a standard KDE application needs. With this technique, starting an application becomes much faster
       because now only the application itself needs to be linked whereas otherwise both the application as well as all the libaries it uses  need
       to be linked.

DISADVANTAGES

       The  process name of applications started via kdeinit4 is "kdeinit4". This problem can be corrected to a degree by changing the application
       name as shown by ps. However, applications like killall will only see kdeinit4 as the process name.  To	workaround  this,  use	kdekillall
       (from kdesdk/scripts) for applications started via kdeinit4.

OPTIONS

       --help Show help about options

       --no-fork
	      Do not fork, i.e. do not exit until all the executed programs ends

       --no-kded
	      Do not start kded

       --suicide
	      Terminate when no KDE applications are left running

       +programs
	      runs the programs handling requests

       programs
	      runs the programs without handling requests

USAGE

       A standard way to run this program is by simply specifying the following command at the prompt kdeinit4 program or kdeinit4 +program

FILES

       /tmp/kde-$USER/kdeinit4_$INSTANCE
	      ...

ENVIRONMENT VARIABLES

       $HOME  Specifies the home directory of the current user

       $KDE_HOME_READONLY
	      Specifies if the home directory of the current user is read only

       $KDE_IS_PRELINKED
	      If set, tells kdeinit4 that the KDE programs are pre-linked.

	      (Prelinking is a process that allows you to speed up the process of dynamic linking.)

       $KDE_DISPLAY
	      If set, tells kdeinit4 that it is running on a KDE desktop.

SEE ALSO

       kded, kdekillall

BUGS

       There are probably tons of bugs. Use bugs.kde.org: http://bugs.kde.org to report them.

AUTHORS

       Waldo Bastian <bastian@kde.org>, Mario Weilguni <mweilguni@sime.com>, Lubos Lunak <l.lunak@kde.org>.

								    2008-10-03							       KDEINIT4(8)

UNIX and Linux RSS News