summaryrefslogtreecommitdiff
path: root/src/metacity.schemas
blob: e8aa7b3494b711f18fdad216969e5a2ecee40d4e (plain)
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
<gconfschemafile>
  <schemalist>

    <!-- General preferences -->        

    <schema>
      <key>/schemas/apps/metacity/general/focus_mode</key>
      <applyto>/apps/metacity/general/focus_mode</applyto>
      <owner>metacity</owner>
      <type>string</type>
      <default>click</default>
      <locale name="C">
         <short>Window focus mode</short>
         <long>
          The window focus mode indicates how windows are activated. 
          It has three possible values; "click" means windows must 
          be clicked in order to focus them, "sloppy" means windows
          are focused when the mouse enters the window, and "mouse" means
          windows are focused when the mouse enters the window and 
          unfocused when the mouse leaves the window.
         </long>
      </locale>
    </schema>

    <schema>
      <key>/schemas/apps/metacity/general/theme</key>
      <applyto>/apps/metacity/general/theme</applyto>
      <owner>metacity</owner>
      <type>string</type>
      <default>Atlanta</default>
      <locale name="C">
         <short>Current theme</short>
         <long>
          The theme determines the appearance of window borders,
          titlebar, and so forth.
         </long>
      </locale>
    </schema>

    <schema>
      <key>/schemas/apps/metacity/general/titlebar_uses_desktop_font</key>
      <applyto>/apps/metacity/general/titlebar_uses_desktop_font</applyto>      
      <owner>metacity</owner>
      <type>bool</type>
      <default>true</default>
      <locale name="C">
         <short>Use standard desktop font in window titles</short>
         <long> 
          If true, ignore the titlebar_font and titlebar_font_size 
          options, and use the standard application font for window 
          titles.
         </long>
      </locale>
    </schema>

    <schema>
      <key>/schemas/apps/metacity/general/titlebar_font</key>
      <applyto>/apps/metacity/general/titlebar_font</applyto>   
      <owner>metacity</owner>
      <type>string</type>
      <!-- no default is deliberate - we want to be unset by default -->
      <locale name="C">
         <short>Window title font</short>
         <long>
          A font description string describing a font for window
          titlebars. The size from the description
          will only be used if the titlebar_font_size option is set 
          to 0, however. Also, this option is disabled if the
          titlebar_uses_desktop_font option is set to true.
          By default, titlebar_font is unset, causing Metacity to fall 
          back to the desktop font even if titlebar_uses_desktop_font 
          is false.
         </long>
      </locale>
    </schema>

    <schema>
      <key>/schemas/apps/metacity/general/titlebar_font_size</key>
      <applyto>/apps/metacity/general/titlebar_font_size</applyto>      
      <owner>metacity</owner>
      <type>int</type>
      <default>0</default>
      <locale name="C">
         <short>Window title font size</short>
         <long>
          The size of the font used in window titlebars, in points.
          If set to 0, the size comes from the titlebar_font option 
          or from the desktop-wide default. If set to nonzero, 
          overrides those sizes.
         </long>
      </locale>
    </schema>

    <schema>
      <key>/schemas/apps/metacity/general/num_workspaces</key>
      <applyto>/apps/metacity/general/num_workspaces</applyto>      
      <owner>metacity</owner>
      <type>int</type>
      <default>4</default>
      <locale name="C">
         <short>Number of workspaces</short>
         <long>
          Number of workspaces. Must be more than zero, and 
          has a fixed maximum (to prevent accidentally destroying 
          your desktop by asking for 34 million workspaces).
         </long>
      </locale>
    </schema>

    <!-- Keybindings -->

    <schema>
      <key>/schemas/apps/metacity/keybindings/activate_window_menu</key>
      <applyto>/apps/metacity/keybindings/activate_window_menu</applyto>
      <owner>metacity</owner>
      <type>string</type>
      <default>&lt;Alt&gt;space</default>
      <locale name="C">
         <short>Activate window menu</short>
         <long>
          The keybinding used to activate the window menu.
          The format looks like "&lt;Control&gt;a" or "&lt;Shift&gt;&lt;Alt&gt;F1" or
          "&lt;Release&gt;z" (the last one is for key release). The parser is
          fairly liberal and allows lower or upper case, and also
          abbreviations such as "&lt;Ctl&gt;" and "&lt;Ctrl&gt;". This option can be 
          set to a single string, or a list of strings; if a list, 
          all of the given keybindings will be present. If you set 
          the option to the special string "disabled", then there 
          will be no keybinding for this action.
         </long>
      </locale>
    </schema>

    <schema>
      <key>/schemas/apps/metacity/general/application_based</key>
      <applyto>/apps/metacity/general/application_based</applyto>      
      <owner>metacity</owner>
      <type>bool</type>
      <default>false</default>
      <locale name="C">
         <short>Navigation works in terms of applications not windows</short>
         <long> 
         If true, then Metacity works in terms of applications rather 
         than windows. The concept is a bit abstract, but 
         in general an application-based setup is more like  
         the Mac and less like Windows. When you focus a window 
         in application-based mode, all the windows in the 
         application will be raised. Also, in application-based 
         mode, focus clicks are not passed through to windows 
         in other applications. 
         The existence of this setting is somewhat questionable. 
         But it's better than having settings for all the specific 
         details of application-based vs. window-based, e.g. 
         whether to pass through clicks. Also, application-based mode
         is largely unimplemented at the moment.
         </long>
      </locale>
    </schema>

  </schemalist>  
</gconfschemafile>