- Timestamp:
- 03/22/2020 08:34:34 AM (4 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- dcee7a56
- Parents:
- 1b70960
- Location:
- x/wm
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
x/wm/fluxbox.xml
r1b70960 r97ee53d 34 34 <title>Introduction to Fluxbox</title> 35 35 36 <para>The <application>Fluxbox</application> package contains a window 37 manager.</para> 36 <para> 37 The <application>Fluxbox</application> package contains a window 38 manager. 39 </para> 38 40 39 41 &lfs91_checked; … … 42 44 <itemizedlist spacing="compact"> 43 45 <listitem> 44 <para>Download (HTTP): <ulink url="&fluxbox-download-http;"/></para> 45 </listitem> 46 <listitem> 47 <para>Download (FTP): <ulink url="&fluxbox-download-ftp;"/></para> 48 </listitem> 49 <listitem> 50 <para>Download MD5 sum: &fluxbox-md5sum;</para> 51 </listitem> 52 <listitem> 53 <para>Download size: &fluxbox-size;</para> 54 </listitem> 55 <listitem> 56 <para>Estimated disk space required: &fluxbox-buildsize;</para> 57 </listitem> 58 <listitem> 59 <para>Estimated build time: &fluxbox-time;</para> 46 <para> 47 Download (HTTP): <ulink url="&fluxbox-download-http;"/> 48 </para> 49 </listitem> 50 <listitem> 51 <para> 52 Download (FTP): <ulink url="&fluxbox-download-ftp;"/> 53 </para> 54 </listitem> 55 <listitem> 56 <para> 57 Download MD5 sum: &fluxbox-md5sum; 58 </para> 59 </listitem> 60 <listitem> 61 <para> 62 Download size: &fluxbox-size; 63 </para> 64 </listitem> 65 <listitem> 66 <para> 67 Estimated disk space required: &fluxbox-buildsize; 68 </para> 69 </listitem> 70 <listitem> 71 <para> 72 Estimated build time: &fluxbox-time; 73 </para> 60 74 </listitem> 61 75 </itemizedlist> … … 64 78 65 79 <bridgehead renderas="sect4">Required</bridgehead> 66 <para role="required"><xref linkend="x-window-system"/></para> 80 <para role="required"> 81 <xref linkend="x-window-system"/> 82 </para> 67 83 68 84 <bridgehead renderas="sect4">Optional</bridgehead> … … 70 86 <xref role="runtime" linkend="dbus"/> (runtime), 71 87 <xref linkend="fribidi"/>, and 72 <xref linkend="imlib2"/> (if you wish to use other image formats in addition to XPM) 88 <xref linkend="imlib2"/> (if you wish to use other image formats in 89 addition to XPM) 73 90 </para> 74 91 … … 81 98 <title>Installation of Fluxbox</title> 82 99 83 <para>Install <application>Fluxbox</application> by running the following 84 commands:</para> 100 <para> 101 Install <application>Fluxbox</application> by running the following 102 commands: 103 </para> 85 104 86 105 <screen><userinput>./configure --prefix=/usr && 87 106 make</userinput></screen> 88 107 89 <para>This package does not have a working testsuite.</para> 90 91 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 108 <para> 109 This package does not have a working testsuite. 110 </para> 111 112 <para> 113 Now, as the <systemitem class="username">root</systemitem> user: 114 </para> 92 115 93 116 <screen role="root"><userinput>make install</userinput></screen> … … 101 124 <title>Config Files</title> 102 125 103 <para><filename>~/.fluxbox/init</filename>, 104 <filename>~/.fluxbox/keys</filename>, and 105 <filename>~/.fluxbox/menu</filename></para> 126 <para> 127 <filename>~/.fluxbox/init</filename>, 128 <filename>~/.fluxbox/keys</filename>, and 129 <filename>~/.fluxbox/menu</filename> 130 </para> 106 131 107 132 <indexterm zone="fluxbox fluxbox-config"> … … 122 147 <title>Configuration Information</title> 123 148 124 <para>If <application>Fluxbox</application> is the only Window Manager 125 you want to use, you can start it with an <filename>.xinitrc</filename> 126 file in your home folder. Be sure to backup your 127 current <filename>.xinitrc</filename> before proceeding.</para> 149 <para> 150 If <application>Fluxbox</application> is the only Window Manager 151 you want to use, you can start it with an <filename>.xinitrc</filename> 152 file in your home folder. Be sure to backup your 153 current <filename>.xinitrc</filename> before proceeding. 154 </para> 128 155 129 156 <indexterm zone="fluxbox fluxbox-config"> … … 133 160 <screen><userinput>echo startfluxbox > ~/.xinitrc</userinput></screen> 134 161 135 <para>Or alternatively, if you use a login manager like 136 <application>GDM</application> or <application>LightDM</application> and would 137 like to be able to choose <application>Fluxbox</application> at the login 138 prompt, create a <filename>fluxbox.desktop</filename> file like this.</para> 139 140 <para>As <systemitem class="username">root</systemitem>:</para> 162 <para> 163 Or alternatively, if you use a login manager like 164 <xref linkend="gdm"/> or <xref linkend="lightdm"/>, 165 and would like to be able to choose <application>Fluxbox</application> 166 at the login prompt, create a <filename>fluxbox.desktop</filename> 167 file. As <systemitem class="username">root</systemitem>: 168 </para> 141 169 142 170 <screen role="root"><userinput>mkdir -pv /usr/share/xsessions && … … 150 178 EOF</userinput></screen> 151 179 152 <para>If you didn't install <application>GDM</application>, 153 <application>SDDM</application>, or <application>LightDM</application> 154 in <filename class='directory'>/usr</filename>, 155 then change that command to fit the prefix you chose.</para> 156 157 <para>Now create the <application>Fluxbox</application> configuration 158 files:</para> 180 <para> 181 If you didn't install <xref linkend="gdm"/> or <xref 182 linkend="lightdm"/> in <filename class='directory'>/usr</filename>, 183 then change that command to fit the prefix you chose. 184 </para> 185 186 <para> 187 Now create the <application>Fluxbox</application> configuration files: 188 </para> 159 189 160 190 <screen><userinput>mkdir -v ~/.fluxbox && … … 162 192 cp -v /usr/share/fluxbox/keys ~/.fluxbox/keys</userinput></screen> 163 193 164 <para>To generate the application menu, first you may wish to run 165 <command>fluxbox-generate_menu -h</command>, in order to choose any 166 <replaceable><user_options></replaceable>, then issue:</para> 167 168 <screen><userinput>cd ~/.fluxbox && 194 <para> 195 To generate the application menu, first you may wish to run 196 <command>fluxbox-generate_menu -h</command>, in order to choose any 197 <replaceable><user_options></replaceable>, then issue: 198 </para> 199 200 <screen role="nodump"><userinput>cd ~/.fluxbox && 169 201 fluxbox-generate_menu <replaceable><user_options></replaceable></userinput></screen> 170 202 171 <para>Alternately, copy a pregenerated menu:</para> 203 <para> 204 Alternately, copy a pregenerated menu: 205 </para> 172 206 173 207 <screen><userinput>cp -v /usr/share/fluxbox/menu ~/.fluxbox/menu</userinput></screen> 174 208 175 <para>Menu items are added by editing <filename>~/.fluxbox/menu</filename>. 176 The syntax is explained on the <command>fluxbox</command> man page.</para> 177 178 <para>If you want to use an image as your desktop background, copy the 179 theme you like into <filename class='directory'>~/.fluxbox</filename>. 180 Then add a line to make it use the correct image. In the following 181 command, change <replaceable><theme></replaceable> for the name of 182 the theme you want and change 183 <replaceable></path/to/nice/image.ext></replaceable> to point to 184 the actual image you want to use, where <replaceable>ext</replaceable> 185 must be <quote>xpm</quote>, if <xref linkend="imlib2"/> is not installed 186 to allow other image formats.</para> 187 188 <screen><userinput>cp /usr/share/fluxbox/styles/<theme> ~/.fluxbox/theme && 209 <para> 210 Menu items are added by editing <filename>~/.fluxbox/menu</filename>. 211 The syntax is explained on the <command>fluxbox</command> man page. 212 </para> 213 214 <para> 215 If you want to use an image as your desktop background, copy the 216 theme you like into <filename class='directory'>~/.fluxbox</filename>. 217 Then add a line to make it use the correct image. In the following 218 command, change <replaceable><theme></replaceable> for the name 219 of the theme you want and change 220 <replaceable></path/to/nice/image.ext></replaceable> to point to 221 the actual image you want to use, where <replaceable>ext</replaceable> 222 must be <quote>xpm</quote>, if <xref linkend="imlib2"/> is not installed 223 to allow other image formats. 224 </para> 225 226 <screen role="nodump"><userinput>cp /usr/share/fluxbox/styles/<theme> ~/.fluxbox/theme && 189 227 190 228 sed -i 's,\(session.styleFile:\).*,\1 ~/.fluxbox/theme,' ~/.fluxbox/init && … … 195 233 echo "background.pixmap: </path/to/nice/image.ext>" >> ~/.fluxbox/theme/theme.cfg</userinput></screen> 196 234 197 <para>In some locales the font specified in the theme may not contain the 198 needed characters. This results in menus with blank items. You can fix 199 this by editing <filename>~/.fluxbox/theme</filename> with a text editor 200 and altering it so that it names a suitable font.</para> 235 <para> 236 In some locales the font specified in the theme may not contain the 237 needed characters. This results in menus with blank items. You can fix 238 this by editing <filename>~/.fluxbox/theme</filename> with a text 239 editor and altering it so that it names a suitable font. 240 </para> 201 241 202 242 </sect3> … … 228 268 <term><command>fluxbox</command></term> 229 269 <listitem> 230 <para>is a window manager for <application>X11</application> based 231 on <application>Blackbox</application> 0.61.0.</para> 270 <para> 271 is a window manager for <application>X11</application> based 272 on <application>Blackbox</application> 0.61.0. 273 </para> 232 274 <indexterm zone="fluxbox fluxbox-prog"> 233 275 <primary sortas="b-fluxbox">fluxbox</primary> … … 239 281 <term><command>fbsetbg</command></term> 240 282 <listitem> 241 <para>is a utility that sets the background image. It requires one 242 of the following at runtime: 243 <command>Esetroot</command>, <command>wmsetbg</command>, 244 <xref linkend="feh-prog"/>, <command>hsetroot</command>, 245 <command>chbg</command>, <xref linkend="display"/>, 246 <command>qiv</command>, <command>xv</command>, 247 <command>xsri</command>, <command>xli</command>, or <command>xsetbg</command>. 248 It also requires <xref linkend="which-prog"/> if <command>Esetroot</command> is 249 found.</para> 283 <para> 284 is a utility that sets the background image. It requires one 285 of the following at runtime: 286 <command>Esetroot</command>, <command>wmsetbg</command>, 287 <xref linkend="feh-prog"/>, <command>hsetroot</command>, 288 <command>chbg</command>, <xref linkend="display"/>, 289 <command>qiv</command>, <command>xv</command>, 290 <command>xsri</command>, <command>xli</command>, or 291 <command>xsetbg</command>. It also requires <xref 292 linkend="which-prog"/> if <command>Esetroot</command> is found. 293 </para> 250 294 <indexterm zone="fluxbox fbsetbg"> 251 295 <primary sortas="b-fbsetbg">fbsetbg</primary> … … 257 301 <term><command>fbsetroot</command></term> 258 302 <listitem> 259 <para>is a utility to change root window appearance based on the 260 <application>Blackbox</application> application bsetroot.</para> 303 <para> 304 is a utility to change root window appearance based on the 305 <application>Blackbox</application> application bsetroot. 306 </para> 261 307 <indexterm zone="fluxbox fbsetroot"> 262 308 <primary sortas="b-fbsetroot">fbsetroot</primary> … … 268 314 <term><command>fluxbox-generate_menu</command></term> 269 315 <listitem> 270 <para>is a utility that generates a menu by scanning your 271 <envar>PATH</envar>.</para> 316 <para> 317 is a utility that generates a menu by scanning your 318 <envar>PATH</envar>. 319 </para> 272 320 <indexterm zone="fluxbox fluxbox-generate_menu"> 273 321 <primary sortas="b-fluxbox-generate_menu">fluxbox-generate_menu</primary> … … 279 327 <term><command>startfluxbox</command></term> 280 328 <listitem> 281 <para>is a session startup script that allows for command 282 executions prior to <command>fluxbox</command> starting.</para> 329 <para> 330 is a session startup script that allows for command 331 executions prior to <command>fluxbox</command> starting. 332 </para> 283 333 <indexterm zone="fluxbox startfluxbox"> 284 334 <primary sortas="b-startfluxbox">startfluxbox</primary> … … 290 340 <term><command>fbrun</command></term> 291 341 <listitem> 292 <para>displays a run dialog window.</para> 342 <para> 343 displays a run dialog window. 344 </para> 293 345 <indexterm zone="fluxbox fbrun"> 294 346 <primary sortas="b-fbrun">fbrun</primary> … … 300 352 <term><command>fluxbox-remote</command></term> 301 353 <listitem> 302 <para>provides command line access to key commands for 303 <application>Fluxbox</application>.</para> 354 <para> 355 provides command line access to key commands for 356 <application>Fluxbox</application>. 357 </para> 304 358 <indexterm zone="fluxbox fluxbox-remote"> 305 359 <primary sortas="b-fluxbox-remote">fluxbox-remote</primary> -
x/wm/icewm.xml
r1b70960 r97ee53d 30 30 <title>Introduction to IceWM</title> 31 31 32 <para><application>IceWM</application> is a window manager with the goals of 33 speed, simplicity, and not getting in the user's way.</para> 32 <para> 33 <application>IceWM</application> is a window manager with the goals of 34 speed, simplicity, and not getting in the user's way. 35 </para> 34 36 35 37 &lfs91_checked; … … 38 40 <itemizedlist spacing="compact"> 39 41 <listitem> 40 <para>Download (HTTP): <ulink url="&icewm-download-http;"/></para> 42 <para> 43 Download (HTTP): <ulink url="&icewm-download-http;"/> 44 </para> 41 45 </listitem> 42 46 <listitem> 43 <para>Download (FTP): <ulink url="&icewm-download-ftp;"/></para> 47 <para> 48 Download (FTP): <ulink url="&icewm-download-ftp;"/> 49 </para> 44 50 </listitem> 45 51 <listitem> 46 <para>Download MD5 sum: &icewm-md5sum;</para> 52 <para> 53 Download MD5 sum: &icewm-md5sum; 54 </para> 47 55 </listitem> 48 56 <listitem> 49 <para>Download size: &icewm-size;</para> 57 <para> 58 Download size: &icewm-size; 59 </para> 50 60 </listitem> 51 61 <listitem> 52 <para>Estimated disk space required: &icewm-buildsize;</para> 62 <para> 63 Estimated disk space required: &icewm-buildsize; 64 </para> 53 65 </listitem> 54 66 <listitem> 55 <para>Estimated build time: &icewm-time;</para> 67 <para> 68 Estimated build time: &icewm-time; 69 </para> 56 70 </listitem> 57 71 </itemizedlist> … … 81 95 <title>Installation of IceWM</title> 82 96 83 <para>Install <application>IceWM</application> by running the following 84 commands:</para> 97 <para> 98 Install <application>IceWM</application> by running the following 99 commands: 100 </para> 85 101 86 102 <screen><userinput>mkdir build && … … 95 111 make</userinput></screen> 96 112 97 <para>This package does not have a working testsuite.</para> 98 99 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 113 <para> 114 This package does not have a working testsuite. 115 </para> 116 117 <para> 118 Now, as the <systemitem class="username">root</systemitem> user: 119 </para> 100 120 <!-- 101 121 <screen role="root"><userinput>cp ../lib/IceWM.jpg lib && … … 136 156 <title>Config Files</title> 137 157 138 <para><filename>~/.icewm/keys</filename>, 158 <para> 159 <filename>~/.icewm/keys</filename>, 139 160 <filename>~/.icewm/menu</filename>, and 140 161 <filename>~/.icewm/preferences</filename>, and … … 144 165 and will be used if you have not copied them to <filename 145 166 class="directory">~/.icewm</filename>. 146 167 </para> 147 168 148 169 … … 172 193 <title>Configuration Information</title> 173 194 174 <para>If <application>IceWM</application> is the only Window Manager you 175 want to use, you can start it with an <filename>.xinitrc</filename> file 176 in your home folder. Be sure to backup your current 177 <filename>.xinitrc</filename> before proceeding.</para> 195 <para> 196 If <application>IceWM</application> is the only Window Manager you 197 want to use, you can start it with an <filename>.xinitrc</filename> file 198 in your home folder. Be sure to backup your current 199 <filename>.xinitrc</filename> before proceeding. 200 </para> 178 201 179 202 <indexterm zone="icewm icewm-config"> … … 183 206 <screen><userinput>echo icewm-session > ~/.xinitrc</userinput></screen> 184 207 185 <para>Now create the <application>IceWM</application> configuration 186 files:</para> 208 <para> 209 Now create the <application>IceWM</application> configuration files: 210 </para> 187 211 188 212 <screen><userinput>mkdir -v ~/.icewm && … … 193 217 cp -v /usr/share/icewm/winoptions ~/.icewm/winoptions</userinput></screen> 194 218 195 <para>You can now edit these files to meet your requirements. In 196 particular, review the <filename>preferences</filename> file. You can use 197 <command>Logout -> Restart-IceWM</command> on the main menu to load your 198 changed preferences, but changes to the background only take effect when 199 <application>IceWM</application> is started.</para> 200 201 <para>At this point you can <emphasis>either</emphasis> modify the 202 traditional menu files to suit your requirements, <emphasis>or</emphasis> 203 use the newer <command>icewm-menu-fdo</command> described later.</para> 204 205 <para>The syntax of the menus is explained in the help files, which you 206 can access by running <command>help</command> from the menu, but some of 207 the detail is out of date and the default selections in the menus (a few 208 old applications on the main menu, everything else on the 209 <command>Programs</command> menu) will benefit from being updated to meet 210 your needs. The following examples are provided to encourage you to 211 think about how you wish to organise your menus. Please note the 212 following:</para> 219 <para> 220 You can now edit these files to meet your requirements. In particular, 221 review the <filename>preferences</filename> file. You can use 222 <command>Logout -> Restart-IceWM</command> on the main menu to load 223 your changed preferences, but changes to the background only take 224 effect when <application>IceWM</application> is started. 225 </para> 226 227 <para> 228 At this point you can <emphasis>either</emphasis> modify the 229 traditional menu files to suit your requirements, 230 <emphasis>or</emphasis> use the newer 231 <command>icewm-menu-fdo</command> described later. 232 </para> 233 234 <para> 235 The syntax of the menus is explained in the help files, which you can 236 access by running <command>help</command> from the menu, but some of 237 the detail is out of date and the default selections in the menus (a 238 few old applications on the main menu, everything else on the 239 <command>Programs</command> menu) will benefit from being updated to 240 meet your needs. The following examples are provided to encourage you 241 to think about how you wish to organise your menus. Please note the 242 following: 243 </para> 213 244 214 245 <itemizedlist> 215 246 <listitem> 216 <para>If a program listed in the menu has not been installed, it will 217 not appear when the menu is displayed. Similarly, if the program 218 exists but the specified icon does not, no icon will be displayed in 219 the menu.</para> 220 </listitem> 221 <listitem> 222 <para>The icons can be either <filename>.xpm</filename> or 223 <filename>.png</filename> files, and there is no need to specify the 224 extension. If the icon is located in the "library" 225 (<filename class="directory">/usr/share/icewm/icons</filename>) there 226 is no need to specifiy the path.</para> 227 </listitem> 228 <listitem> 229 <para>Most programs are in sub-menus, and the main menu will always 230 append entries for <literal>windows, help, settings, logout</literal> 231 at the bottom.</para> </listitem> 232 <listitem> 233 <para>An icon for <application>firefox</application> was copied to 234 the library directory and given a meaningful name. The icon for 235 <application>xine</application> is <filename>xine.xpm</filename> 236 which was installed to a pixmap directory.</para> 237 </listitem> 238 <listitem> 239 <para>The default toolbar is not altered.</para> 247 <para> 248 If a program listed in the menu has not been installed, it will 249 not appear when the menu is displayed. Similarly, if the program 250 exists but the specified icon does not, no icon will be displayed 251 in the menu. 252 </para> 253 </listitem> 254 <listitem> 255 <para> 256 The icons can be either <filename>.xpm</filename> or 257 <filename>.png</filename> files, and there is no need to specify 258 the extension. If the icon is located in the "library" 259 (<filename class="directory">/usr/share/icewm/icons</filename>) 260 there is no need to specifiy the path. 261 </para> 262 </listitem> 263 <listitem> 264 <para> 265 Most programs are in sub-menus, and the main menu will always 266 append entries for 267 <literal>windows, help, settings, logout</literal> 268 at the bottom. 269 </para> 270 </listitem> 271 <listitem> 272 <para> 273 An icon for <application>firefox</application> was copied to 274 the library directory and given a meaningful name. The icon for 275 <application>xine</application> is <filename>xine.xpm</filename> 276 which was installed to a pixmap directory. 277 </para> 278 </listitem> 279 <listitem> 280 <para> 281 The default toolbar is not altered. 282 </para> 240 283 </listitem> 241 284 </itemizedlist> 242 285 243 <para>If you wish to use this traditional method, there are more examples in 286 <para> 287 If you wish to use this traditional method, there are more examples in 244 288 previous releases of this book (e.g. BLFS-7.8). 245 289 </para> 246 290 247 <para><emphasis>Alternatively</emphasis>, you can create a menu which conforms 248 to the FDO Desktop Menu Specifications, where programs can be found because 249 they have a .desktop file in the XDG_DATA_HOME or XDG_DATA_DIR directories. 250 Unlike most windowmanagers, <application>icewm</application> does not search 251 for programs when the menu is invoked, so if you take this route you will 252 need to rerun the following command after installing or removing programs: 291 <para> 292 <emphasis>Alternatively</emphasis>, you can create a menu which 293 conforms to the FDO Desktop Menu Specifications, where programs can be 294 found because they have a .desktop file in the XDG_DATA_HOME or 295 XDG_DATA_DIR directories. Unlike most windowmanagers, 296 <application>icewm</application> does not search for programs when the 297 menu is invoked, so if you take this route you will need to rerun the 298 following command after installing or removing programs: 253 299 </para> 254 300 255 301 <screen><userinput>icewm-menu-fdo >~/.icewm/menu</userinput></screen> 256 302 257 <para>If you wish to put icons on your desktop, you will need to install 258 a program such as <xref linkend="rox-filer"/> which provides a pinboard. 259 If you do that you will no longer be able to access the menu by 260 right-clicking on the desktop, you will have to use the 261 <application>IceWM</application> button. To ensure that the 262 <application>rox</application> pinboard is running, the following 263 commands will put it in the startup file:</para> 303 <para> 304 If you wish to put icons on your desktop, you will need to install a 305 program such as <xref linkend="rox-filer"/> which provides a pinboard. 306 If you do that you will no longer be able to access the menu by 307 right-clicking on the desktop, you will have to use the 308 <application>IceWM</application> button. To ensure that the 309 <application>rox</application> pinboard is running, the following 310 commands will put it in the startup file: 311 </para> 264 312 265 313 <screen role="nodump"><userinput>cat > ~/.icewm/startup << "EOF" … … 269 317 270 318 <tip> 271 <para>There are a number of keyboard shortcuts in 272 <application>IceWM</application>:</para> 273 <itemizedlist> 274 <listitem> 275 <para>Ctrl + Alt + F<replaceable>N</replaceable> : go to 276 <filename>tty<replaceable>N</replaceable></filename>.</para> 277 </listitem> 278 <listitem> 279 <para>Ctrl + Alt + <replaceable>N</replaceable> : go to desktop 280 number <replaceable>N</replaceable></para> 281 </listitem> 282 <listitem> 283 <para>Ctrl + Alt + Space : open a box on the taskbar where you can 284 key in the name of an application and run it.</para> 285 </listitem> 286 </itemizedlist> 319 <para> 320 There are a number of keyboard shortcuts in 321 <application>IceWM</application>: 322 </para> 323 <itemizedlist> 324 <listitem> 325 <para> 326 Ctrl + Alt + F<replaceable>N</replaceable> : go to 327 <filename>tty<replaceable>N</replaceable></filename>. 328 </para> 329 </listitem> 330 <listitem> 331 <para> 332 Ctrl + Alt + <replaceable>N</replaceable> : go to desktop 333 number <replaceable>N</replaceable> 334 </para> 335 </listitem> 336 <listitem> 337 <para> 338 Ctrl + Alt + Space : open a box on the taskbar where you can 339 key in the name of an application and run it. 340 </para> 341 </listitem> 342 </itemizedlist> 287 343 </tip> 288 344 … … 315 371 <term><command>icehelp</command></term> 316 372 <listitem> 317 <para>is used to display the html manual.</para> 373 <para> 374 is used to display the html manual. 375 </para> 318 376 <indexterm zone="icewm icehelp"> 319 377 <primary sortas="b-icehelp">icehelp</primary> … … 325 383 <term><command>icesh</command></term> 326 384 <listitem> 327 <para>is a command-line window manager which can be used in 328 <filename>~/.icewm/startup</filename>.</para> 385 <para> 386 is a command-line window manager which can be used in 387 <filename>~/.icewm/startup</filename>. 388 </para> 329 389 <indexterm zone="icewm icesh"> 330 390 <primary sortas="b-icesh">icesh</primary> … … 336 396 <term><command>icesound</command></term> 337 397 <listitem> 338 <para>plays audio files on GUI events raised by IceWM.</para> 398 <para> 399 plays audio files on GUI events raised by IceWM. 400 </para> 339 401 <indexterm zone="icewm icesound"> 340 402 <primary sortas="b-icesound">icesound</primary> … … 346 408 <term><command>icewm</command></term> 347 409 <listitem> 348 <para>is the window manager.</para> 410 <para> 411 is the window manager. 412 </para> 349 413 <indexterm zone="icewm icewm-prog"> 350 414 <primary sortas="b-icewm">icewm</primary> … … 356 420 <term><command>icewm-menu-fdo</command></term> 357 421 <listitem> 358 <para>can create a file in a format suitable for an IceWM menu, which 359 lists those programs currently installed in a layout conforming to the 360 FDO Desktop Menu Specifications.</para> 422 <para> 423 can create a file in a format suitable for an IceWM menu, which 424 lists those programs currently installed in a layout conforming to 425 the FDO Desktop Menu Specifications. 426 </para> 361 427 <indexterm zone="icewm icewm-menu-fdo"> 362 428 <primary sortas="b-icewm-menu-fdo">icewm-menu-fdo</primary> … … 368 434 <term><command>icewm-session</command></term> 369 435 <listitem> 370 <para>runs icewmbg, icewm, icewmtray, startup, shutdown (i.e. startup 371 and shutdown scripts are run if installed).</para> 436 <para> 437 runs icewmbg, icewm, icewmtray, startup, shutdown (i.e. startup 438 and shutdown scripts are run if installed). 439 </para> 372 440 <indexterm zone="icewm icewm-session"> 373 441 <primary sortas="b-icewm-session">icewm-session</primary> … … 379 447 <term><command>icewm-set-gnomewm</command></term> 380 448 <listitem> 381 <para>is a script to set the <application>GNOME</application>windowmanager to 382 <application>icewm</application> using <application>gconftool</application>. 449 <para> 450 is a script to set the <application>GNOME</application> window 451 manager to <application>icewm</application> using 452 <application>gconftool</application>. 383 453 </para> 384 454 <indexterm zone="icewm icewm-set-gnomewm"> … … 391 461 <term><command>icewmbg</command></term> 392 462 <listitem> 393 <para>is used to set the background, according to the various 394 <literal>DesktopBackground</literal> settings in the preferences.</para> 463 <para> 464 is used to set the background, according to the various 465 <literal>DesktopBackground</literal> settings in the preferences. 466 </para> 395 467 <indexterm zone="icewm icewmbg"> 396 468 <primary sortas="b-icewmbg">icewmbg</primary> … … 402 474 <term><command>icewmhint</command></term> 403 475 <listitem> 404 <para>is used internally.</para> 476 <para> 477 is used internally. 478 </para> 405 479 <indexterm zone="icewm icewmhint"> 406 480 <primary sortas="b-icewmhint">icewmhint</primary> … … 412 486 <term><command>icewmtray</command></term> 413 487 <listitem> 414 <para>provides the tray.</para> 488 <para> 489 provides the tray. 490 </para> 415 491 <indexterm zone="icewm icewmtray"> 416 492 <primary sortas="b-icewmtray">icewmtray</primary> -
x/wm/openbox.xml
r1b70960 r97ee53d 47 47 </listitem> 48 48 <listitem> 49 <para>Download MD5 sum: &openbox-md5sum; 50 </para> 49 <para> 50 Download MD5 sum: &openbox-md5sum; 51 </para> 51 52 </listitem> 52 53 <listitem> … … 94 95 <title>Installation of Openbox</title> 95 96 96 <note><para>If XORG_PREFIX is not <filename class='directory'>/usr</filename>, 97 tell <command>gcc</command> about it:</para> 98 99 <screen><userinput>export LIBRARY_PATH=$XORG_PREFIX/lib</userinput></screen> 97 <note> 98 <para> 99 If XORG_PREFIX is not <filename class='directory'>/usr</filename>, 100 tell <command>gcc</command> about it: 101 </para> 102 103 <screen><userinput>export LIBRARY_PATH=$XORG_PREFIX/lib</userinput></screen> 104 100 105 </note> 101 106 102 <para>If you only installed the Python 3 PyXDG module convert one of the 103 scripts to Python 3:</para> 107 <para> 108 If you only installed the Python 3 PyXDG module convert one of the 109 scripts to Python 3: 110 </para> 104 111 105 112 <screen><userinput>2to3-&python3-majorver; -w data/autostart/openbox-xdg-autostart && … … 155 162 156 163 <para> 157 /etc/xdg/openbox/autostart, /etc/xdg/openbox/menu.xml, /etc/xdg/openbox/rc.xml, 158 ~/.config/openbox/autostart, ~/.config/openbox/menu.xml and ~/.config/openbox/rc.xml 164 <filename>/etc/xdg/openbox/autostart</filename>, 165 <filename>/etc/xdg/openbox/menu.xml</filename>, 166 <filename>/etc/xdg/openbox/rc.xml</filename>, 167 <filename>~/.config/openbox/autostart</filename>, 168 <filename>~/.config/openbox/menu.xml</filename> and 169 <filename>~/.config/openbox/rc.xml</filename> 159 170 </para> 160 171 … … 272 283 If you like to have the numlock key set whan you start Xorg, install 273 284 <!-- 13-12-11 numlockx not found on the KDE website. This URL is OK ? --> 274 <ulink url="http://ftp.de.debian.org/debian/pool/main/n/numlockx/numlockx_1.2.orig.tar.gz">Numlockx</ulink> and 275 add that to your xinitrc. Another useful application is 276 <xref linkend="dbus"/>: 285 <ulink url= 286 "http://ftp.de.debian.org/debian/pool/main/n/numlockx/numlockx_1.2.orig.tar.gz"> 287 Numlockx</ulink> and add that to your xinitrc. Another useful 288 application is <xref linkend="dbus"/>: 277 289 </para> 278 290 -
x/wm/other-wms.xml
r1b70960 r97ee53d 14 14 </sect1info> 15 15 16 <title>Other Window Manager s</title>16 <title>Other Window Manager</title> 17 17 18 <para><command>twm</command> is the Tab Window Manager. This is the default 19 window manager installed by the <xref linkend="x-window-system"/> 20 packages.</para> 21 22 <para><command>mwm</command> is the Motif® Window Manager. It is an 23 <application>OSF/Motif®</application> clone packaged and installed with 24 <!-- <xref linkend="lesstif"/>.</para>--> 25 <ulink url="http://sourceforge.net/projects/lesstif/">LessTif</ulink>.</para> 18 <para> 19 <command>mwm</command> is the Motif Window Manager. It has been 20 released under a LGPL license in 2012, together with the Motif 21 library, and is available at 22 <ulink url="https://sourceforge.net/projects/motif/"/>. 23 </para> 26 24 27 25 </sect1> -
x/wm/sawfish.xml
r1b70960 r97ee53d 30 30 <title>Introduction to sawfish</title> 31 31 32 <para>The <application>sawfish</application> package contains a window 33 manager. This is useful for organizing and displaying windows where all 34 window decorations are configurable and all user-interface policy is 35 controlled through the extension language.</para> 32 <para> 33 The <application>sawfish</application> package contains a window 34 manager. This is useful for organizing and displaying windows where all 35 window decorations are configurable and all user-interface policy is 36 controlled through the extension language. 37 </para> 36 38 37 39 &lfs91_checked; … … 40 42 <itemizedlist spacing="compact"> 41 43 <listitem> 42 <para>Download (HTTP): <ulink url="&sawfish-download-http;"/></para> 43 </listitem> 44 <listitem> 45 <para>Download (FTP): <ulink url="&sawfish-download-ftp;"/></para> 46 </listitem> 47 <listitem> 48 <para>Download MD5 sum: &sawfish-md5sum;</para> 49 </listitem> 50 <listitem> 51 <para>Download size: &sawfish-size;</para> 52 </listitem> 53 <listitem> 54 <para>Estimated disk space required: &sawfish-buildsize;</para> 55 </listitem> 56 <listitem> 57 <para>Estimated build time: &sawfish-time;</para> 44 <para> 45 Download (HTTP): <ulink url="&sawfish-download-http;"/> 46 </para> 47 </listitem> 48 <listitem> 49 <para> 50 Download (FTP): <ulink url="&sawfish-download-ftp;"/> 51 </para> 52 </listitem> 53 <listitem> 54 <para> 55 Download MD5 sum: &sawfish-md5sum; 56 </para> 57 </listitem> 58 <listitem> 59 <para> 60 Download size: &sawfish-size; 61 </para> 62 </listitem> 63 <listitem> 64 <para> 65 Estimated disk space required: &sawfish-buildsize; 66 </para> 67 </listitem> 68 <listitem> 69 <para> 70 Estimated build time: &sawfish-time; 71 </para> 58 72 </listitem> 59 73 </itemizedlist> … … 75 89 <title>Installation of sawfish</title> 76 90 77 <para>Install <application>sawfish</application> by running the following 78 commands:</para> 91 <para> 92 Install <application>sawfish</application> by running the following 93 commands: 94 </para> 79 95 80 96 <screen><userinput>./configure --prefix=/usr --with-pango && 81 97 make</userinput></screen> 82 98 83 <para>This package does not come with a test suite.</para> 84 85 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 99 <para> 100 This package does not come with a test suite. 101 </para> 102 103 <para> 104 Now, as the <systemitem class="username">root</systemitem> user: 105 </para> 86 106 87 107 <screen role="root"><userinput>make install</userinput></screen> … … 92 112 <title>Command Explanations</title> 93 113 94 <para><parameter>- -disable-themer</parameter>: This 95 option prevents building the <application>sawfish</application> themer. 96 This program was not migrated to <application>GTK-2</application>.</para> 97 98 <para><option>- -with-audiofile</option>: This command directs 99 <application>sawfish</application> to use 100 <filename class="libraryfile">libaudiofile</filename> 101 for sound manipulation.</para> 102 103 <para><option>- -with-esd</option>: This command directs 104 <application>sawfish</application> to use the Enlightened Sound 105 Daemon.</para> 114 <para> 115 <parameter>- -disable-themer</parameter>: This 116 option prevents building the <application>sawfish</application> themer. 117 This program was not migrated to <application>GTK-2</application>. 118 </para> 119 120 <para> 121 <option>- -with-audiofile</option>: This command directs 122 <application>sawfish</application> to use 123 <filename class="libraryfile">libaudiofile</filename> 124 for sound manipulation. 125 </para> 126 127 <para> 128 <option>- -with-esd</option>: This command directs 129 <application>sawfish</application> to use the Enlightened Sound 130 Daemon. 131 </para> 106 132 107 133 </sect2> … … 117 143 </indexterm> 118 144 119 <para>Be sure to backup your current <filename>.xinitrc</filename> 120 before proceeding.</para> 145 <para> 146 Be sure to backup your current <filename>.xinitrc</filename> 147 before proceeding. 148 </para> 121 149 122 150 <screen><userinput>cat >> ~/.xinitrc << "EOF" … … 124 152 EOF</userinput></screen> 125 153 126 <para>Optionally, you can use a Display Manager, such as <xref 127 linkend="lxdm"/>.</para> 128 129 <para>From the developers: <quote>The default menu binding is somewhat 130 obscure; you must middle-click on the background to bring up the menus. 131 (If you have a two-button mouse, try clicking both buttons 132 simultaneously)</quote>. You can find this at <ulink 133 url="http://download.tuxfamily.org/sawfish/themes/FAQ.html/">sawfish's 134 FAQ</ulink>.</para> 154 <para> 155 Optionally, you can use a Display Manager, such as <xref 156 linkend="lxdm"/>. 157 </para> 158 159 <para> 160 From the developers: <quote>The default menu binding is somewhat 161 obscure; you must middle-click on the background to bring up the menus. 162 (If you have a two-button mouse, try clicking both buttons 163 simultaneously)</quote>. You can find this at <ulink 164 url="http://download.tuxfamily.org/sawfish/themes/FAQ.html/">sawfish's 165 FAQ</ulink>. 166 </para> 135 167 136 168 </sect3> … … 172 204 <term><filename>sawfish</filename></term> 173 205 <listitem> 174 <para>is the extensible window manager using a 175 <application>Lisp</application>-based scripting language.</para> 206 <para> 207 is the extensible window manager using a 208 <application>Lisp</application>-based scripting language. 209 </para> 176 210 <indexterm zone="sawfish sawfish-prog"> 177 211 <primary sortas="b-sawfish">sawfish</primary> … … 183 217 <term><filename>sawfish-about</filename></term> 184 218 <listitem> 185 <para>is the <application>sawfish</application> about window.</para> 219 <para> 220 is the <application>sawfish</application> about window. 221 </para> 186 222 <indexterm zone="sawfish sawfish-about"> 187 223 <primary sortas="b-sawfish-about">sawfish-about</primary> … … 193 229 <term><filename>sawfish-client</filename></term> 194 230 <listitem> 195 <para>allows you to connect to a window manager process and 196 evaluate arbitrary <application>Lisp</application> forms.</para> 231 <para> 232 allows you to connect to a window manager process and 233 evaluate arbitrary <application>Lisp</application> forms. 234 </para> 197 235 <indexterm zone="sawfish sawfish-client"> 198 236 <primary sortas="b-sawfish-client">sawfish-client</primary> … … 204 242 <term><filename>sawfish-config</filename></term> 205 243 <listitem> 206 <para>is the <application>sawfish</application> configuration manager.</para> 244 <para> 245 is the <application>sawfish</application> configuration manager. 246 </para> 207 247 <indexterm zone="sawfish sawfish-config-prog"> 208 248 <primary sortas="b-sawfish-config-prog">sawfish-config</primary> … … 215 255 <listitem> 216 256 <para> 217 is a script to run <application>KDE4</application> using <application>sawfish</application>. 257 is a script to run <application>KDE4</application> using 258 <application>sawfish</application>. 218 259 </para> 219 260 <indexterm zone="sawfish sawfish-kde4-session"> … … 240 281 <listitem> 241 282 <para> 242 is a script to run <application>mate</application> using <application>sawfish</application>. 283 is a script to run <application>mate</application> using 284 <application>sawfish</application>. 243 285 </para> 244 286 <indexterm zone="sawfish sawfish-mate-session"> … … 252 294 <listitem> 253 295 <para> 254 is a script to run <application>Lumina</application> using <application>sawfish</application>. 296 is a script to run <application>Lumina</application> using 297 <application>sawfish</application>. 255 298 </para> 256 299 <indexterm zone="sawfish sawfish-lumina-session"> … … 264 307 <listitem> 265 308 <para> 266 is a script to run <application>xfce</application> using <application>sawfish</application>. 309 is a script to run <application>xfce</application> using 310 <application>sawfish</application>. 267 311 </para> 268 312 <indexterm zone="sawfish sawfish-xfce-session"> -
x/wm/wm.xml
r1b70960 r97ee53d 11 11 <title>Window Managers</title> 12 12 13 <sect1 id="wm-introduction"> 14 <?dbhtml filename="introduction.html" ?> 13 <!-- 14 $LastChangedBy$ 15 $Date$/date> 16 --> 15 17 16 <sect1info> 17 <othername>$LastChangedBy$</othername> 18 <date>$Date$</date> 19 </sect1info> 20 21 <title>Introduction</title> 22 23 <para>Window Managers and Desktop Environments are the primary user 18 <para> 19 Window Managers and Desktop Environments are the primary user 24 20 interfaces into the <application>X</application> Window System. A window 25 21 manager is a program that controls the appearance of windows and provides 26 22 the means by which the user can interact with them. A Desktop Environment 27 23 provides a more complete interface to the operating system, and provides a 28 range of integrated utilities and applications.</para> 24 range of integrated utilities and applications. 25 </para> 29 26 30 <para>There are many Window Managers available. Some of the more well 27 <para> 28 There are many Window Managers available. Some of the more well 31 29 known ones include <application>fvwm2</application>, <application>Window 32 30 Maker</application>, <application>AfterStep</application>, 33 31 <application>Enlightenment</application>, 34 32 <application>Sawfish</application>, 35 and <application>Blackbox</application>.</para> 33 and <application>Blackbox</application>. 34 </para> 36 35 37 <para>The Desktop Environments available for Linux are 36 <para> 37 The Desktop Environments available for Linux are 38 38 <application>GNOME</application>, <application>KDE</application>, and 39 <application>XFce</application>.</para> 39 <application>XFce</application>. 40 </para> 40 41 41 <para>Choosing a Window Manager or Desktop Environment is highly 42 <para> 43 Choosing a Window Manager or Desktop Environment is highly 42 44 subjective. The choice depends on the look and feel of the packages, the 43 45 resources (RAM, disk space) required, and the utilities included. One web 44 46 site that provides a very good summary of what is available, screenshots, 45 and their respective features is <ulink url="http://xwinman.org/">Window 46 Managers for X</ulink>.</para> 47 and their respective features is 48 <ulink url="http://www.xwinman.org/"> 49 Window Managers for X 50 </ulink>. 51 </para> 47 52 48 <para>In this chapter, the installation instructions of several Window 53 <para> 54 In this chapter, the installation instructions of several Window 49 55 Managers and one lightweight Desktop Environment are presented. Later in 50 56 the book, both <application>KDE</application> and 51 <application>GNOME</application> have their own sections.</para> 52 53 </sect1> 57 <application>GNOME</application> have their own sections. 58 </para> 54 59 55 60 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="fluxbox.xml"/>
Note:
See TracChangeset
for help on using the changeset viewer.