summaryrefslogtreecommitdiffstats
path: root/doc/kalarm
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-12-07 19:12:32 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-12-07 19:12:32 -0600
commit9a8a1e372f4f35ebdc75da2a2cddc06a77e44fc4 (patch)
treefd03284328d7fbf88ace3e6c4ebe86c6a2d28ba5 /doc/kalarm
parentf2a152bb4c76b5e29e782c5ecf49a2b44fdd87e5 (diff)
downloadtdepim-9a8a1e372f4f35ebdc75da2a2cddc06a77e44fc4.tar.gz
tdepim-9a8a1e372f4f35ebdc75da2a2cddc06a77e44fc4.zip
Rename KDEHOME and KDEDIR
Diffstat (limited to 'doc/kalarm')
-rw-r--r--doc/kalarm/index.docbook18
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/kalarm/index.docbook b/doc/kalarm/index.docbook
index 0e0d6844f..8385c1bea 100644
--- a/doc/kalarm/index.docbook
+++ b/doc/kalarm/index.docbook
@@ -3915,30 +3915,30 @@ to trigger them when they become due.</para>
<para>What configuration files does &kalarm; use?</para>
</question>
<answer>
-<para>The file <filename>$KDEHOME/share/config/kalarmrc</filename>
+<para>The file <filename>$TDEHOME/share/config/kalarmrc</filename>
holds your &kalarm; preferences.</para>
<para>The calendar file which stores your pending alarms is
-<filename>$KDEHOME/share/apps/kalarm/calendar.ics</filename>, unless
+<filename>$TDEHOME/share/apps/kalarm/calendar.ics</filename>, unless
a different calendar file is specified in the preferences file by a
<parameter>Calendar</parameter> entry in the
<parameter>General</parameter> section.</para>
<para>The calendar file which stores your expired alarms is
-<filename>$KDEHOME/share/apps/kalarm/expired.ics</filename>, unless
+<filename>$TDEHOME/share/apps/kalarm/expired.ics</filename>, unless
a different calendar file is specified in the preferences file by an
<parameter>ExpiredCalendar</parameter> entry in the
<parameter>General</parameter> section.</para>
<para>The calendar file which stores your alarm templates is
-<filename>$KDEHOME/share/apps/kalarm/template.ics</filename>, unless
+<filename>$TDEHOME/share/apps/kalarm/template.ics</filename>, unless
a different calendar file is specified in the preferences file by a
<parameter>TemplateCalendar</parameter> entry in the
<parameter>General</parameter> section.</para>
<para>Details of alarms currently being displayed are stored in the
calendar file
-<filename>$KDEHOME/share/apps/kalarm/displaying.ics</filename>.</para>
+<filename>$TDEHOME/share/apps/kalarm/displaying.ics</filename>.</para>
</answer>
</qandaentry>
@@ -3949,7 +3949,7 @@ calendar file
daemon</application> use?</para>
</question>
<answer>
-<para>The file <filename>$KDEHOME/share/config/kalarmdrc</filename>
+<para>The file <filename>$TDEHOME/share/config/kalarmdrc</filename>
holds your <application>alarm daemon</application> preferences,
together with details of the &kalarm; client application.</para>
</answer>
@@ -4111,14 +4111,14 @@ if your &kde; is installed in <filename>/opt/kde2</filename>:</para>
<warning><para>If you install &kalarm; into a folder different from
where &kde; is installed, it will not run correctly unless you make
its location known to &kde;. To do this, you must prefix the
-<envar>KDEDIRS</envar> environment variable with &kalarm;'s location,
+<envar>TDEDIRS</envar> environment variable with &kalarm;'s location,
each time before you start &kde;.</para>
<para>For example, if &kde; is installed in
-<literal>/opt/kde</literal>, <envar>KDEDIRS</envar> might normally
+<literal>/opt/kde</literal>, <envar>TDEDIRS</envar> might normally
be set to <literal>/etc/opt/kde:/opt/kde</literal>. If you install
&kalarm; into <literal>/usr/local</literal>, you would need to set
-<envar>KDEDIRS</envar> to
+<envar>TDEDIRS</envar> to
<literal>/usr/local:/etc/opt/kde:/opt/kde</literal> before starting
&kde;.</para></warning>