Annotated edit history of
session-properties(1) version 1, including all changes.
View license author blame.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
SESSION-PROPERTIES |
|
|
2 |
!!!SESSION-PROPERTIES |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
AUTHOR |
|
|
8 |
---- |
|
|
9 |
!!NAME |
|
|
10 |
|
|
|
11 |
|
|
|
12 |
session-properties - a non-CORBA version of the session-properties-capplet. |
|
|
13 |
!!SYNOPSIS |
|
|
14 |
|
|
|
15 |
|
|
|
16 |
__session-properties__ [[ __--init-session-settings__ ] |
|
|
17 |
[[ __--warner__ ] |
|
|
18 |
!!DESCRIPTION |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
__session-properties__ monitors the state of current |
|
|
22 |
GNOME running applications and capplets. It allows you to |
|
|
23 |
change the style and priority of each program. You can shut |
|
|
24 |
down applications, if you wish, and those applications will |
|
|
25 |
be removed from your GNOME session. You can also use Session |
|
|
26 |
Properties to kill a GNOME application and remove it from |
|
|
27 |
session management so it will not be restarted when you log |
|
|
28 |
in next time. Of course, there are other ways to kill an |
|
|
29 |
application, such as using an explicit kill command, but |
|
|
30 |
they would not prevent an application from being restarted |
|
|
31 |
if it has the Respawn Style. The only way to permanently |
|
|
32 |
remove such an application is with the Remove |
|
|
33 |
button. |
|
|
34 |
!!OPTIONS |
|
|
35 |
|
|
|
36 |
|
|
|
37 |
__--init-session-settings__ |
|
|
38 |
|
|
|
39 |
|
|
|
40 |
Initialize session settings. |
|
|
41 |
|
|
|
42 |
|
|
|
43 |
__--warner__ |
|
|
44 |
|
|
|
45 |
|
|
|
46 |
Only display warnings. |
|
|
47 |
!!AUTHOR |
|
|
48 |
|
|
|
49 |
|
|
|
50 |
This manual page was written by Christian Marillat |
|
|
51 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.