summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorTimothy Pearson <[email protected]>2012-02-26 14:41:36 -0600
committerTimothy Pearson <[email protected]>2012-02-26 14:41:36 -0600
commit618f2521c3406cb4cb02689d93f5f950e5f94027 (patch)
treec5e419510449dcb70d20502eccbd28a4bc2dc622 /doc
parent3862d9bc994791982446306877a8071d764ccd87 (diff)
downloadtdebase-618f2521c3406cb4cb02689d93f5f950e5f94027.tar.gz
tdebase-618f2521c3406cb4cb02689d93f5f950e5f94027.zip
Rename kde-config to tde-config
Diffstat (limited to 'doc')
-rw-r--r--doc/faq/configkde.docbook2
-rw-r--r--doc/kate/advanced.docbook2
-rw-r--r--doc/userguide/index.docbook2
-rw-r--r--doc/userguide/under-the-hood.docbook2
4 files changed, 4 insertions, 4 deletions
diff --git a/doc/faq/configkde.docbook b/doc/faq/configkde.docbook
index b51090b66..8f687f69b 100644
--- a/doc/faq/configkde.docbook
+++ b/doc/faq/configkde.docbook
@@ -198,7 +198,7 @@ usually a folder named <filename class="directory">.kde</filename>
folder. If you want scripts to be executed for all &tde; users, you can
put them under <filename class="directory">$<envar>TDEDIR</envar>/env/</filename>, where $<envar>TDEDIR</envar> is the prefix &tde; was
installed to (you can find this out using the command
-<userinput><command>kde-config</command> --prefix</userinput>).</para>
+<userinput><command>tde-config</command> --prefix</userinput>).</para>
<para>If you wish to start a program after &tde; has started, you may want to use the
<filename class="directory">Autostart</filename> folder. To add
entries to the <filename class="directory">Autostart</filename> folder:
diff --git a/doc/kate/advanced.docbook b/doc/kate/advanced.docbook
index 224610e62..d16437121 100644
--- a/doc/kate/advanced.docbook
+++ b/doc/kate/advanced.docbook
@@ -653,7 +653,7 @@ only. The requirements is that the script is placed in a folder where &kate;
can find it, along with an optional .desktop file that defines the related
properties. The valid folder are named <filename>katepart/scripts</filename>
in the &tde; data folders. You can find the data folders by running the command
-<command>kde-config <option>--path</option> <parameter>data</parameter></command>
+<command>tde-config <option>--path</option> <parameter>data</parameter></command>
You will usually have at least a system and a personal data folder. Of course
scripts in the system data folder are available to all users on the system,
while those in the personal folder are available for you only.</para>
diff --git a/doc/userguide/index.docbook b/doc/userguide/index.docbook
index 03a886cd6..ecf4ee3d7 100644
--- a/doc/userguide/index.docbook
+++ b/doc/userguide/index.docbook
@@ -227,7 +227,7 @@ Although this guide is revised periodically, those traditional terms might still
<varlistentry>
<term>&tde; prefix</term>
<listitem><para>&tde; installs into its own folder tree, which is found by
-running the command <userinput><command>kde-config</command> <option>--prefix</option></userinput>. This folder is referred to
+running the command <userinput><command>tde-config</command> <option>--prefix</option></userinput>. This folder is referred to
by the environment variable $<envar>TDEDIR</envar> and possibly
$<envar>TDEDIRS</envar>.</para>
</listitem>
diff --git a/doc/userguide/under-the-hood.docbook b/doc/userguide/under-the-hood.docbook
index 97a9f839c..e42b06da9 100644
--- a/doc/userguide/under-the-hood.docbook
+++ b/doc/userguide/under-the-hood.docbook
@@ -23,7 +23,7 @@ class="directory">.kde/share/config</filename> (replace
the global ones are in the <filename
class="directory">share/config</filename> sub-directory of &tde;'s
installation path. (You can find this path by running the command
-<command>kde-config --prefix</command>.) Their filenames typically
+<command>tde-config --prefix</command>.) Their filenames typically
end in rc (without an initial period), for example <filename>kopeterc</filename>.</para>
<warning><para>