From f99c7f6c54aaf96eec1f58c2eaacb46edc6de8cd Mon Sep 17 00:00:00 2001 From: Darrell Anderson Date: Mon, 6 Jan 2014 02:25:18 +0100 Subject: Rename kdebugdialog -> tdedebugdialog --- doc/userguide/under-the-hood.docbook | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'doc/userguide/under-the-hood.docbook') diff --git a/doc/userguide/under-the-hood.docbook b/doc/userguide/under-the-hood.docbook index 62ab1a5ec..6757cc8d9 100644 --- a/doc/userguide/under-the-hood.docbook +++ b/doc/userguide/under-the-hood.docbook @@ -385,17 +385,17 @@ window. - + -&kdebugdialog; - Controlling &tde;'s Debugging Output +&tdedebugdialog; - Controlling &tde;'s Debugging Output - + Basic Usage -&kdebugdialog; is not in the &kmenu; by default. You will need to run +&tdedebugdialog; is not in the &kmenu; by default. You will need to run it from the shell or from the mini-CLI with -the command kdebugdialog. -&kdebugdialog; pops up a window with a long list of debugging areas. Each +the command tdedebugdialog. +&tdedebugdialog; pops up a window with a long list of debugging areas. Each area has a checkbox that you can check or uncheck in order to enable or disable debugging output for that part of &tde;. @@ -416,13 +416,13 @@ buttons which will cause &tde; to produce a mountain of debugging output, or very little. - -KDebugDialog in full mode + +TDEDebugDialog in full mode - + -In full mode, which is what you get when you start kdebugdialog as -kdebugdialog +In full mode, which is what you get when you start tdedebugdialog as +tdedebugdialog , the same list of debugging areas as in plain mode is available, but you can select only one at a time from a drop-down box. You may then independently set the output -- cgit v1.2.1