1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
|
<!--
<?xml version="1.0" ?>
<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
"dtd/kdex.dtd">
-->
<chapter id="tips">
<title
>Useful tips</title>
<qandaset>
<qandaentry>
<question>
<para
>Reading documentation in &kde;</para>
</question>
<answer>
<para
>Pop up the <guilabel
>Run Command</guilabel
> window (<keycombo action="simul"
>&Alt;<keycap
>F2</keycap
></keycombo
> by default) and type: <itemizedlist>
<listitem>
<para
><command
>man:<replaceable
>command</replaceable
></command
> for man pages. It even unpacks on the fly if the man pages are gzipped.</para>
</listitem>
<listitem>
<para
><command
>info:<replaceable
>command</replaceable
></command
> for info pages.</para>
</listitem>
<listitem>
<para
><command
>help:<replaceable
>kdeappname</replaceable
></command
> for &kde; application help pages.</para>
</listitem>
</itemizedlist>
</para>
<para
>You can also enter any of these in the <guilabel
>Location</guilabel
> text box in &konqueror;.</para>
<para
>Or you can use the <application
>&kde; Help Centre</application
> if you are using &kde; 2. Simply start the <application
>&kde; Help Centre</application
> by clicking on the icon (the blue book with the yellow key) on the toolbar. Once the <application
>&kde; Help Centre</application
> has loaded, the window on the left will contain an entry called <guilabel
>Unix manual pages</guilabel
>. Click once on this entry, and you can browse through all the installed manual pages on your system.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Move or resize windows quickly</para>
</question>
<answer>
<para
>To move a window, use <keycombo action="simul"
>&Alt;<mousebutton
>left</mousebutton
></keycombo
> mouse button. <keycombo action="simul"
>&Alt;<mousebutton
>right</mousebutton
></keycombo
> mouse button will resize the window. Last but not least, <keycombo action="simul"
>&Alt;<mousebutton
>middle</mousebutton
></keycombo
> mouse button raises/lowers the window. The <application
>&kde; Control Centre</application
> allows you to change these mouse bindings.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Killing windows in &kde;</para>
</question>
<answer>
<para
>There is a standard keybinding (<keycombo action="simul"
>&Ctrl;&Alt;&Esc;</keycombo
>) that gives you a skull & crossbones cursor. Click that cursor on a window to kill it. The keybindings are viewable/changeable from the <application
>&kde; Control Centre</application
>. <caution
><para
>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.</para
></caution>
<!-- fixme: use only if necessary; processes might remain --></para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>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?</para>
</question>
<answer>
<para
>These kind of locks tend to occur when an application locks up while it has a so called <quote
>mouse/keyboard grab</quote
>. When that happens you can try to select a virtual text console with <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F1</keycap
></keycombo
> and login. With the following command you will get a list of all running processes:</para>
<screen
><userinput
> <command
>ps</command
> <option
>-aux</option
> | <command
>more</command
></userinput
></screen>
<para
>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:</para>
<screen
><userinput
> <command
>kill</command
> <option
>-9</option
> <replaceable
>pid</replaceable
></userinput
></screen>
<para
>Here <replaceable
>pid</replaceable
> is the process id of the process, which is the first number on each line reported by <command
>ps</command
> <option
>-aux</option
>.</para>
<para
>You can switch back to the desktop with <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F7</keycap
></keycombo
> (or <keycap
>F8</keycap
> through <keycap
>F9</keycap
> depending on your operating system) to see if things work again. When you press <keycombo action="simul"
>&Alt;<keycap
>Tab</keycap
></keycombo
> 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.</para>
<para
>Good candidates to kill are: the application you were working with, &kicker;, &klipper; and &kdesktop;.</para>
</answer>
</qandaentry>
<!-- fixme: how to do in KDE2.x
<qandaentry>
<question>
<para
>Switching window managers on the fly in &kde; 1.x</para>
</question>
<answer>
<para
>If you want to switch your window manager on the fly, type the
following into a terminal window: <command
>kwmcom
go:<replaceable
>blackbox</replaceable
></command
>. This switches to
Blackbox, but you can substitute any window manager you like.</para>
</answer>
</qandaentry>
-->
</qandaset>
</chapter>
|
