From 0b8ca6637be94f7814cafa7d01ad4699672ff336 Mon Sep 17 00:00:00 2001 From: Darrell Anderson Date: Tue, 21 Jan 2014 22:06:48 -0600 Subject: Beautify docbook files --- tde-i18n-en_GB/docs/tdebase/faq/tips.docbook | 175 +++++---------------------- 1 file changed, 30 insertions(+), 145 deletions(-) (limited to 'tde-i18n-en_GB/docs/tdebase/faq/tips.docbook') diff --git a/tde-i18n-en_GB/docs/tdebase/faq/tips.docbook b/tde-i18n-en_GB/docs/tdebase/faq/tips.docbook index 9f7b4e80e26..af3d0ad2b57 100644 --- a/tde-i18n-en_GB/docs/tdebase/faq/tips.docbook +++ b/tde-i18n-en_GB/docs/tdebase/faq/tips.docbook @@ -5,199 +5,84 @@ --> -Useful tips +Useful tips -Reading documentation in &kde; +Reading documentation in &kde; -Pop up the Run Command window (&Alt;F2 by default) and type: +Pop up the Run Command window (&Alt;F2 by default) and type: -man:command for man pages. It even unpacks on the fly if the man pages are gzipped. +man:command for man pages. It even unpacks on the fly if the man pages are gzipped. -info:command for info pages. +info:command for info pages. -help:kdeappname for &kde; application help pages. +help:kdeappname for &kde; application help pages. -You can also enter any of these in the Location text box in &konqueror;. -Or you can use the &kde; Help Centre if you are using &kde; 2. Simply start the &kde; Help Centre by clicking on the icon (the blue book with the yellow key) on the toolbar. Once the &kde; Help Centre has loaded, the window on the left will contain an entry called Unix manual pages. Click once on this entry, and you can browse through all the installed manual pages on your system. +You can also enter any of these in the Location text box in &konqueror;. +Or you can use the &kde; Help Centre if you are using &kde; 2. Simply start the &kde; Help Centre by clicking on the icon (the blue book with the yellow key) on the toolbar. Once the &kde; Help Centre has loaded, the window on the left will contain an entry called Unix manual pages. Click once on this entry, and you can browse through all the installed manual pages on your system. -Move or resize windows quickly +Move or resize windows quickly -To move a window, use &Alt;left mouse button. &Alt;right mouse button will resize the window. Last but not least, &Alt;middle mouse button raises/lowers the window. The &kde; Control Centre allows you to change these mouse bindings. +To move a window, use &Alt;left mouse button. &Alt;right mouse button will resize the window. Last but not least, &Alt;middle mouse button raises/lowers the window. The &kde; Control Centre allows you to change these mouse bindings. -Killing windows in &kde; +Killing windows in &kde; -There is a standard keybinding (&Ctrl;&Alt;&Esc;) that gives you a skull & crossbones cursor. Click that cursor on a window to kill it. The keybindings are viewable/changeable from the &kde; Control Centre. Using this option kills the program forcibly. Data may be lost, and some processes related to the program may remain active. Use only as a last resort. +There is a standard keybinding (&Ctrl;&Alt;&Esc;) that gives you a skull & crossbones cursor. Click that cursor on a window to kill it. The keybindings are viewable/changeable from the &kde; Control Centre. Using this option kills the program forcibly. Data may be lost, and some processes related to the program may remain active. Use only as a last resort. -What if something is so wrong that I ca not even get the skull & crossbones cursor? How do I get out of a total lockup? +What if something is so wrong that I ca not even get the skull & crossbones cursor? How do I get out of a total lockup? -These kind of locks tend to occur when an application locks up while it has a so called mouse/keyboard grab. When that happens you can try to select a virtual text console with &Ctrl;&Alt;F1 and login. With the following command you will get a list of all running processes: - - ps | more - -By killing the process that has the mousegrab, your desktop will come to life again. Unfortunately you ca not see which process that is, so you will have to find out through trial and error. To kill a process use: - - kill pid - -Here pid is the process id of the process, which is the first number on each line reported by ps . - -You can switch back to the desktop with &Ctrl;&Alt;F7 (or F8 through F9 depending on your operating system) to see if things work again. When you press &Alt;Tab you should get a response from the window manager. If not, you need to get back to the text console and try to kill another process. - -Good candidates to kill are: the application you were working with, &kicker;, &klipper; and &kdesktop;. +These kind of locks tend to occur when an application locks up while it has a so called mouse/keyboard grab. When that happens you can try to select a virtual text console with &Ctrl;&Alt;F1 and login. With the following command you will get a list of all running processes: + + ps | more + +By killing the process that has the mousegrab, your desktop will come to life again. Unfortunately you ca not see which process that is, so you will have to find out through trial and error. To kill a process use: + + kill pid + +Here pid is the process id of the process, which is the first number on each line reported by ps . + +You can switch back to the desktop with &Ctrl;&Alt;F7 (or F8 through F9 depending on your operating system) to see if things work again. When you press &Alt;Tab you should get a response from the window manager. If not, you need to get back to the text console and try to kill another process. + +Good candidates to kill are: the application you were working with, &kicker;, &klipper; and &kdesktop;.