From 5ddc4d2fa0a88092a515275b93575458cd36324d Mon Sep 17 00:00:00 2001
From: Timothy Pearson <kb9vqf@pearsoncomputing.net>
Date: Wed, 16 Nov 2011 17:59:29 -0600
Subject: Rename startkde to starttde

---
 doc/faq/install.docbook              | 22 +++++++++++-----------
 doc/kdm/index.docbook                |  2 +-
 doc/userguide/index.docbook          |  8 ++++----
 doc/userguide/kde-for-admins.docbook | 18 +++++++++---------
 4 files changed, 25 insertions(+), 25 deletions(-)

(limited to 'doc')

diff --git a/doc/faq/install.docbook b/doc/faq/install.docbook
index 8de7055b9..8dc1227ea 100644
--- a/doc/faq/install.docbook
+++ b/doc/faq/install.docbook
@@ -377,16 +377,16 @@ calling them, you can only benefit fully from &kde;'s advanced
 features if you use the &kde; window manager and its helper
 programs.</para>
 <para>In order to make it easy for you, we have provided a simple
-script called <filename>startkde</filename> which gets installed in <filename
+script called <filename>starttde</filename> which gets installed in <filename
 class="directory">$<envar>KDEDIR</envar>/bin</filename> and is therefore in your
 path.</para>
 <para>Edit the file <filename>.xinitrc</filename> in your home folder (make a backup
 copy first!), remove everything that looks like calling a window
-manager, and insert <command>startkde</command> instead.  Restart the &X-Server;.  If you use
+manager, and insert <command>starttde</command> instead.  Restart the &X-Server;.  If you use
 &kdm;/<application>xdm</application>, you will have to edit the file <filename>.xsession</filename> instead of
 <filename>.xinitrc</filename>.  And if there is no <filename>.xinitrc</filename> or <filename>.xsession</filename> in your home
 folder, simply create a new one with just one line containing
-<command>startkde</command>.
+<command>starttde</command>.
 <note>
 <para>Some systems (notably &RedHat; &Linux;) use <filename>.Xclients</filename>
 instead.</para>
@@ -420,19 +420,19 @@ can lead to problems if you are not careful. </para>
 </qandaentry>
 
 <qandaentry>
-<question id="startkde">
+<question id="starttde">
 <para>How do I start &kde;?</para>
 </question>
 <answer>
 <para>The most comfortable method to start &kde; is to use the
-<filename>startkde</filename> script.  Simply put the line
-<command>startkde</command> at the end of your <filename>.xsession</filename>
+<filename>starttde</filename> script.  Simply put the line
+<command>starttde</command> at the end of your <filename>.xsession</filename>
 file (or your <filename>.xinitrc</filename> or <filename>.Xclients</filename>
 file if you are not using &kdm; or <application>xdm</application>).  Please
 also remove the lines that start your previous window manager.  If there is no
 <filename>.xsession</filename>, <filename>.xinitrc</filename>, or
 <filename>.Xclients</filename> in your home folder, simply create a new one
-that contains just one line: <command>startkde</command>.</para>
+that contains just one line: <command>starttde</command>.</para>
 </answer>
 </qandaentry>
 <!-- Still needed?
@@ -524,16 +524,16 @@ screen, so this option will not work.</para>
 
 <qandaentry>
 <question>
-<para><command>startkde</command> fails with <errorname>can not connect to X
+<para><command>starttde</command> fails with <errorname>can not connect to X
 server</errorname>.  What is wrong?</para>
 </question>
 <answer>
-<para>You probably tried to start the X server with <command>startkde</command>.  The X
+<para>You probably tried to start the X server with <command>starttde</command>.  The X
 server is started with <command>startx</command>.
-<command>startkde</command> is the 
+<command>starttde</command> is the 
 script that should be run from your <filename>.xinitrc</filename>, <filename>.xsession</filename>, or
 <filename>.Xclients</filename> to activate the window manager and the necessary server
-daemons for &kde;.  See also <xref linkend="startkde"/>.</para>
+daemons for &kde;.  See also <xref linkend="starttde"/>.</para>
 </answer>
 </qandaentry>
 
diff --git a/doc/kdm/index.docbook b/doc/kdm/index.docbook
index 070fc7958..ee73b16a6 100644
--- a/doc/kdm/index.docbook
+++ b/doc/kdm/index.docbook
@@ -126,7 +126,7 @@ the next step</para>
 <filename>~/.xinitrc</filename> to start your preferred window manager
 or desktop environment.</para>
 <para>For &kde; you should enter:</para>
-<screen><userinput>startkde</userinput></screen>
+<screen><userinput>starttde</userinput></screen>
 <para>For other window managers or desktop environments, you should
 look in their documentation for the correct command.</para>
 </step>
diff --git a/doc/userguide/index.docbook b/doc/userguide/index.docbook
index b039979ce..66e312069 100644
--- a/doc/userguide/index.docbook
+++ b/doc/userguide/index.docbook
@@ -357,8 +357,8 @@ programs here (and not links to removable media, like CDs).</para>
 </sect1info>
 
 <title>Logging In and Logging Out</title>
-<para>Basic KDM &amp; startkde stuff.</para>
-<!-- Not sure what exactly to say about startkde and where to say it -->
+<para>Basic KDM &amp; starttde stuff.</para>
+<!-- Not sure what exactly to say about starttde and where to say it -->
 <!-- (Phil) -->
 <para>There are two ways to log into &kde;: graphically and via the
 command line. We'll look at them both briefly:</para>
@@ -382,12 +382,12 @@ it is done, &kde; will be ready to use.</para>
 
 <sect2 id="logging-in-via-cmdline">
 <title>Logging in via the Command Line</title>
-<indexterm><primary><command>startkde</command></primary></indexterm>
+<indexterm><primary><command>starttde</command></primary></indexterm>
 <indexterm><primary><command>startx</command></primary></indexterm>
 
 <para>If you prefer using the command line, you can log in to &kde;
 with the <command>startx</command> command. Add the line
-<userinput>exec startkde</userinput> to the
+<userinput>exec starttde</userinput> to the
 <filename>.xinitrc</filename> file in your home folder (create it
 if it does not exist), save the file, and then run
 <command>startx</command>. &kde; should start in the same way as if
diff --git a/doc/userguide/kde-for-admins.docbook b/doc/userguide/kde-for-admins.docbook
index da0d91496..47195f284 100644
--- a/doc/userguide/kde-for-admins.docbook
+++ b/doc/userguide/kde-for-admins.docbook
@@ -811,7 +811,7 @@ Startup - <filename>/etc/X11/xdm/Xstartup</filename> - prepare as root
 Session - <filename>/etc/X11/xdm/Xsession</filename> - starts session as user
 </member>
 <member>
-= For a KDE session: <command>kde</command> or <command>startkde</command>
+= For a KDE session: <command>kde</command> or <command>starttde</command>
 </member>
 <member>
 = If present <filename>~/.xsession</filename> or <filename>~/.xinitrc</filename>
@@ -823,13 +823,13 @@ Reset - <filename>/etc/X11/xdm/Xreset</filename> - after session finished
 
 </sect2>
 
-<sect2 id="startkde">
-<title>The &kde; Startup Script: <command>startkde</command></title>
+<sect2 id="starttde">
+<title>The &kde; Startup Script: <command>starttde</command></title>
 
 <para>The &kde; startup sequence starts with the
-<filename>startkde</filename> script. In most cases this script gets called
+<filename>starttde</filename> script. In most cases this script gets called
 from the display manager (&kdm;) once the user has been authenticated. Their
-are two very important lines in the <filename>startkde</filename>
+are two very important lines in the <filename>starttde</filename>
 script:</para>
 
 <programlisting>
@@ -945,7 +945,7 @@ programs started as <acronym>KLM</acronym>s.</para>
 <para>When <command>tdeinit</command> starts for the first time it will
 launch <command>dcopserver</command>, <command>klauncher</command>, and
 <command>kded</command>, as well as any additional programs specified on its
-command line in the <command>startkde</command> script, normally
+command line in the <command>starttde</command> script, normally
 <command>kcminit</command> and <command>knotify</command>.</para>
 
 </sect2>
@@ -1184,7 +1184,7 @@ class="username">root</systemitem>.</para>
 <varlistentry><term>$<envar>KDEWM</envar></term><listitem><para>If the
 <envar>KDEWM</envar> environment variable has been set, then it will
 be used as &kde;'s window manager within the
-<command>startkde</command> script instead of &twin;.</para>
+<command>starttde</command> script instead of &twin;.</para>
 </listitem>
 </varlistentry>
 
@@ -1626,7 +1626,7 @@ class="directory">$<envar>KDEDIR</envar>/apps/kdesktop/DesktopLinks</filename>
 merged)</para></listitem>
 
 <listitem><para>Distribution Specific SUSE Linux copies certain icons
-in startkde.theme from <filename
+in starttde.theme from <filename
 class="directory">/opt/trinity/share/config/SuSE/default/</filename></para></listitem>
 
 </itemizedlist>
@@ -2356,7 +2356,7 @@ there.</para>
 <title>Making it Work</title>
 
 Making It Work
-KDE 3.2: Set $KDEDIRS from startkde script
+KDE 3.2: Set $KDEDIRS from starttde script
 Distribute profiles to all clients
 
 </para>
-- 
cgit v1.2.3